Network service management method, related apparatus, and system

ABSTRACT

A network service management method includes receiving, by a second NFVO, a first request sent by a first NFVO; and establishing, by the second NFVO, a connection between the nested network service instance and the composite network service instance and a connection between the nested network service instance and a member instance in the composite network service instance based on the service access point instance and the information about the service access point instance, and establishing a network connection between the nested network service instance and a member instance in the nested network service instance based on the service access point instance and the information about the service access point instance.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2017/119978, filed on Dec. 29, 2017, the disclosure of which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

This application relates to the field of cloud computing technologies,and in particular, to a network service management method, a relatedapparatus, and a system.

BACKGROUND

Network functions virtualization (NFV) is a technology in which atelecommunications network operator uses a virtualization technology inthe information technology (IT) field to perform software-hardwaredecoupling for implementing some telecommunications network functions ina universal server, switch, and memory, so as to rapidly and efficientlydeploy a network service (NS), and reduce investment costs CAPEX andoperation costs OPEX. In this technology, the telecommunications networkfunction needs to be implemented by software, can be run on hardware ofthe universal server, and can be migrated, instantiated, and deployed atdifferent physical locations of a network as required, and no new deviceneeds to be installed.

In NFV, a virtualized network service (NS) may be, for example, an IPmultimedia subsystem (IMS) or an evolved packet core (EPC) service. OneNS may include one or more virtualized network functions (VNF). The VNFis software implementation of a network function that can be deployed onan NFV infrastructure. When an NS is deployed, a service requestapparatus, such as an operations support system and business supportsystem (OSS/BSS), needs to provide an apparatus, such as an NFVorchestrator (NFVO), for a service and provide an NS descriptor (NSD).The NS descriptor mainly describes a topology structure of the NS and adescriptor for each member instance included in the NS. In the topologystructure, a virtual link (VL) is used to describe a connection betweenmember instances.

Currently, NFV standardization mainly focuses on dynamic management andorchestration (MANO) of virtualized network functions (VNF) andvirtualized resources. Functions in a MANO framework are formulated bythe NFV interface and architecture (IFA) working group of the EuropeanCommunications Standards Institute (ETSI). A MANO function architectureis shown in FIG. 1.

(1) NFV orchestrator (NFVO): The NFVO mainly manages and processes anetwork service descriptor (NSD) and a virtualized network functionforwarding graph (VNFFG), performs life cycle management for a networkservice, and cooperates with a VNF manager (VNFM) to perform life cyclemanagement for a VNF and implement a global view function forvirtualized resources. In addition, the NFVO may further communicatewith a virtualized infrastructure manager (VIM), to allocate and/orreserve a virtualized resource, and exchange configuration and statusinformation of the virtualized resource.

(2) VNF manager (VNFM): The VNFM performs life cycle management for thevirtualized network function VNF, where the life cycle managementincludes virtualized network function descriptor (VNFD) management, VNFinstantiation, VNF instance scaling (including scaling out/up andscaling in/down), VNF instance healing, and VNF instance termination.The VNFM can further receive a scaling (scaling) policy delivered by theNFVO, to implement VNF auto scaling.

(3) Virtualized infrastructure manager (VIM): The VIM is mainlyresponsible for managing (including reserving and allocating) a hardwareresource and a virtualized resource at an infrastructure layer,monitoring a status of the virtualized resource, reporting a fault, andproviding a virtualized resource pool for an upper-layer application.

(5) Operations support system and business support system (OSS/BSS): TheOSS/BSS supports various end-to-end teleservices, and mainly refers toan existing operations support system and business support systemOSS/BSS of an operator. The OSS/BSS may load the NSD onto the NFVO andinitiate an NS instantiation request to the NFVO.

(6) Element management system (Element Manager, EM): The EM performs aconventional fault, configuration, user, performance, and securitymanagement (fault management, configuration management, accountingmanagement, performance management, security management, FCAPS) functionfor the VNF.

(7) Virtualized network function (VNF): The VNF is equivalent to aphysical network function (physical network function, PNF) in aconventional non-virtualized network, and for example, is a virtualizedEPC node (an MME, an SGW, a PGW, or the like). Functional behavior and astatus of a network function are unrelated to virtualization. In an NFVtechnology, it is expected that the VNF and the PNF have same functionalbehavior and same external interfaces.

The VNF may include a plurality of lower-level VNF components (VNFC).Therefore, one VNF may be deployed on a plurality of virtual machines(Virtual Machine, VM), and each VM carries a function of one VNFcomponent. Alternatively, the VNF may be deployed on one VM.

(8) NFV infrastructure (NFVI): The NFVI includes a hardware resource, avirtualized resource, and a virtualization layer. From the perspectiveof the VNF, the virtualization layer and the hardware resourceconstitute an entity that can provide a required virtualized resource.

In a scenario in which a network service is provided across a pluralityof administrative domains (multiple administrative domains), if all ofmember VNF instances and nested NS instances in a composite NS instanceare available, a consumer NFVO (Consumer NFVO) connects the member VNFinstances to the nested NS instances in the composite NS instance.However, a virtual link (VL) information model defined in an existingETSI NFV standard is designed merely from the perspective that theconsumer NFVO performs network connection.

SUMMARY

This application provides a network service management method, a relatedapparatus, and a system. A virtual link information model is definedfrom the perspective of a nested network service instance. This can meeta requirement for establishing a network connection from the perspectiveof the nested network service instance.

According to a first aspect, this application provides a network servicemanagement method, applied to a first NFVO (that is, a consumer NFVO)side. The method may include: sending, by a first NFVO, a first requestto a second NFVO, where the first request may be used to request tocreate a nested NS instance in a composite NS instance. The firstrequest carries information (that is, SapInfo) about a SAP instanceassociated with the nested NS instance. The SapInfo may be used by thesecond NFVO to establish, based on the SAP instance, a connectionbetween the nested NS instance and the composite NS instance and aconnection between the nested NS instance and a member instance in thecomposite NS instance, and is further used by the second NFVO toestablish, based on the SAP instance, a connection relationship to amember instance in the nested NS instance.

According to a second aspect, this application provides a networkservice management method, applied to a second NFVO (that is, a providerNFVO) side. The method may include: receiving, by a second NFVO, a firstrequest sent by a first NFVO, where the first request may be used torequest to create a nested NS instance in a composite NS instance. Thefirst request carries information (that is, SapInfo) about a SAPinstance associated with the nested NS instance. The SapInfo may be usedby the second NFVO to establish, based on the SAP instance, a connectionbetween the nested NS instance and the composite NS instance and aconnection between the nested NS instance and a member instance in thecomposite NS instance, and is further used by the second NFVO toestablish, based on the SAP instance, a connection relationship to amember instance in the nested NS instance. Then, the second NFVOestablishes, based on the SAP instance and the SapInfo, the connectionbetween the nested NS instance and the composite NS instance and theconnection between the nested NS instance and the member instance in thecomposite NS instance, and establishes, based on the SAP instance andthe SapInfo, the connection relationship to the member instance in thenested NS instance.

It may be understood that, by implementing the methods described in thefirst aspect and the second aspect, the SapInfo is carried in a request(namely, the first request) used to create the nested NS instance, andthe provider NFVO may be indicated to establish external and internalnetwork connections of the nested NS instance based on the SapInfo fromthe perspective of the nested NS instance. This can meet a requirementfor establishing a network connection from the perspective of the nestedNS.

With reference to the first aspect or the second aspect, the followingdescribes specific implementation of the SapInfo in this application.

In this application, the SapInfo may include two parts: firstinformation and second information. The first information isspecifically used to describe an external virtual link informationmodel, and may be used by the second NFVO to establish a connectionbetween the nested NS instance and the member instance that is in thecomposite NS instance that is (externally) connected to the nested NSinstance through the SAP instance. The second information isspecifically used to describe an internal virtual link informationmodel, and may be used by the second NFVO to establish a connectionbetween the nested NS instance and the member instance that is in thenested NS instance and that is (internally) connected to the nested NSinstance through the SAP instance.

In this application, the first information may include an identifier ofan external virtual link instance, an identifier of a port through whichthe SAP instance is connected to the external virtual link instance, andan identifier of a peer connection point connected to the SAP instancethrough the external virtual link instance. The peer connection pointconnected to the SAP instance through the external virtual link instancemay be an external connection point that is of the member instance inthe composite network service instance and that is connected to the SAPinstance through the external virtual link instance, for example, anexternal connection point VnfExtCp of a VNF instance, an externalconnection point PnfExtCp of a PNF instance, or a service access pointSAP of another nested NS instance. The peer connection point connectedto the SAP instance through the external virtual link instance mayalternatively be a service access point SAP of the composite NSinstance.

In this application, the second information may include an identifier ofan internal virtual link instance, a port through which the SAP instanceis connected to the internal virtual link instance, and an identifier ofa peer connection point connected to the SAP instance through theinternal virtual link instance. The peer connection point connected tothe SAP instance through the internal virtual link instance may be anexternal connection point that is of the member instance in the nestednetwork service instance and that is connected to the SAP instancethrough the internal virtual link instance, for example, an externalconnection point VnfExtCp of a VNF instance, an external connectionpoint PnfExtCp of a PNF instance, or a service access point SAP of asub-nested NS instance.

Information about the peer connection point may not be reflected in theinternal virtual link information model, to ensure information isolationbetween different administrative domains. To be specific, the secondinformation may alternatively include an identifier of a second virtuallink instance and a port through which the SAP instance is connected tothe internal virtual link instance, and does not include an identifierof a peer connection point connected to the SAP instance through theinternal virtual link instance. In other words, an internal peerconnection point that is internally connected to the nested NS instancethrough the SAP instance is invisible to the outside (that is, thecomposite NS instance and another member instance in the composite NSinstance).

With reference to the first aspect or the second aspect, in someembodiments, as soon as all member instances in the composite NSinstance are available (available), the second NFVO that manages thenested NS may establish, based on the virtual link information model,connections indicated by a virtual link information model.

1. In this application, the second NFVO may establish, based on the SAPinstance of the nested NS instance, connections indicated by theexternal virtual link information model in at least one of the followingmanners:

Manner 1: The second NFVO establishes, based on the first information inthe SapInfo, a connection between the SAP instance and a SAP instancethat is of the composite NS instance and that is externally connected tothe SAP instance through the external virtual link instance.

Manner 2: The second NFVO establishes, based on the first information inthe SapInfo, a connection between the SAP instance and a SAP instancethat is of the another nested NS instance in the composite NS instanceand that is externally connected to the SAP instance through theexternal virtual link instance.

Manner 3: The second NFVO establishes, based on the first information inthe SapInfo, a connection between the SAP instance and the externalconnection point that is of the VNF instance in the composite NSinstance and that is externally connected to the SAP instance throughthe external virtual link instance.

Manner 4: The second NFVO establishes, based on the first information inthe SapInfo, a connection between the SAP instance and the externalconnection point that is of the PNF instance in the composite NSinstance and that is externally connected to the SAP instance throughthe external virtual link instance.

2. In this application, the second NFVO may establish, based on the SAPinstance of the nested NS instance, connections indicated by theinternal virtual link information model in at least one of the followingmanners:

Manner 1: The second NFVO establishes, based on the second informationin the SapInfo, a connection between the SAP instance and a SAP instancethat is of the sub-nested NS instance in the nested NS instance and thatis internally connected to the SAP instance through the internal virtuallink instance.

Manner 2: The second NFVO establishes, based on the second informationin the SapInfo, a connection between the SAP instance and the externalconnection point that is of the VNF instance in the nested NS instanceand that is internally connected to the SAP instance through theinternal virtual link instance.

Manner 3: The second NFVO establishes, based on the second informationin the SapInfo, a connection between the SAP instance and the externalconnection point that is of the PNF instance in the nested NS instanceand that is internally connected to the SAP instance through theinternal virtual link instance.

With reference to the first aspect or the second aspect, in someembodiments, the first NFVO may send a second request to the secondNFVO. Specifically, the second request may be used to request to updatethe nested NS instance in the composite NS instance. Specifically, thesecond request may carry the SapInfo associated with the nested NSinstance. Correspondingly, the second NFVO receives the second requestsent by the first NFVO. The second NFVO may update, based on the SapInfothat is associated with the nested NS instance and that is carried inthe second request, the connection between the nested NS instance andthe composite NS instance that is externally connected to the nested NSinstance based on the SAP instance and the connection between the nestedNS instance and the member instance that is in the composite NS instanceand that is externally connected to the nested NS instance based on theSAP instance, or update the connection between the nested NS instanceand the member instance that is in the nested NS instance and that isinternally connected to the nested NS instance based on the SAPinstance.

Herein, the SapInfo is specifically used to describe a virtual linkinformation model associated with the SAP instance, and may be used bythe second NFVO to update network connections associated with the nestedNS instance, to be specific, update the connection between the nested NSinstance and the composite NS instance that is externally connected tothe nested NS instance based on the SAP instance and the connectionbetween the nested NS instance and the member instance that is in thecomposite NS instance and that is externally connected to the nested NSinstance based on the SAP instance, or update the connection between thenested NS instance and the member instance that is in the nested NSinstance and that is internally connected to the nested NS instancebased on the SAP instance.

Specifically, the updating network connections associated with thenested NS instance may include at least one of the following:establishing a new network connection associated with the nested NSinstance, modifying an existing network connection associated with thenested NS instance, or removing an existing network connectionassociated with the nested NS instance.

It may be understood that, the SapInfo is carried in a request (namely,the second request) used to update the nested NS instance, and theprovider NFVO may be indicated to update external and internal networkconnections of the nested NS instance based on the SapInfo from theperspective of the nested NS instance. This can better meet arequirement for updating a network connection from the perspective of anested NS.

With reference to the first aspect or the second aspect, in someembodiments, the first NFVO may send a third request to the second NFVO.Specifically, the third request may be used to request to use anexisting nested NS instance managed by the second NFVO. The thirdrequest carries information about a SAP instance that is of the existingnested NS instance and that is newly added in the composite NS instancemanaged by the first NFVO. The information about the newly added SAPinstance may be used by the second NFVO to establish, based on the newlyadded SAP instance, a network connection that is of the existing nestedNS instance and that is in the composite NS instance. Correspondingly,the second NFVO receives the third request sent by the first NFVO. Thesecond NFVO may establish, based on the newly added SAP instance and theinformation about the newly added SAP instance, the network connectionthat is of the existing nested NS instance and that is in the compositeNS instance.

It may be understood that, in a scenario in which an NS instance isshared, SapInfo is carried in a notification (namely, the third request)of determining to use the NS instance, and the provider NFVO may beindicated to establish a network connection, in the composite NSinstance managed by the consumer NFVO, of the nested NS instance basedon the SapInfo from the perspective of the nested NS instance. This canmeet a requirement for establishing, from the perspective of an existingnested NS, a network connection associated with the nested NS instance.

According to a third aspect, this application provides an apparatus. Theapparatus may implement a function of a consumer NFVO, that is, theforegoing first NFVO. The apparatus may include a processing unit and acommunications unit.

The communications unit may be configured to receive a request that isused to create a composite NS instance and that is sent by a sender (forexample, an OSS/BSS).

The communications unit may be configured to send a first request to aprovider NFVO (the foregoing second NFVO), where the first request isused to request the provider NFVO to create a nested NS instance in thecomposite NS instance.

The processing unit may be configured to: create a member instance (thatis, another member instance) other than the nested NS instance in thecomposite NS instance, and establish a network connection between memberinstances.

Specifically, the first request carries information about a SAP instanceassociated with the nested NS instance. The information about the SAPinstance may be used by the provider NFVO to establish, based on the SAPinstance, a connection between the nested NS instance and the compositeNS instance and a connection between the nested NS instance and themember instance in the composite NS instance, and is further used by theprovider NFVO to establish, based on the SAP instance, a connectionrelationship to a member instance in the nested NS instance.

In some embodiments, the communications unit may be further configuredto receive a request that is used to update the composite NS instanceand that is sent by the sender (for example, the OSS/BSS). Thecommunications unit may be further configured to send a second requestto the second NFVO, where the second request may be used to request toupdate the nested NS instance in the composite NS instance.Specifically, the second request carries the information about the SAPinstance associated with the nested NS instance, and the informationabout the SAP instance may be used by the second NFVO to update, basedon the SAP instance, a network connection that is associated with thenested NS instance and that is in the composite NS instance. Optionally,the processing unit may be further configured to: update the memberinstance (that is, the another member instance) other than the nested NSinstance in the composite NS instance, and update the network connectionbetween member instances.

In some embodiments, after receiving the request that is used to createthe composite NS instance and that is sent by the sender, thecommunications unit may be further configured to send a third request tothe second NFVO, where the third request may be used to request to usean existing nested NS instance managed by the second NFVO to constitutea composite NS instance. Specifically, the third request carriesinformation about a SAP instance that is of the existing nested NSinstance and that is newly added in the composite NS instance managed bythe first NFVO. The information about the newly added SAP instance maybe used by the second NFVO to establish, based on the newly added SAPinstance, a network connection that is of the existing nested NSinstance and that is in the composite NS instance.

It may be understood that the processing unit and the communicationsunit may be configured to correspondingly perform the method provided inthe first aspect or any possible implementation of the first aspect.Details are not described herein again.

According to a fourth aspect, this application provides an apparatus.The apparatus may implement a provider NFVO, that is, the foregoingsecond NFVO. The apparatus may include a processing unit and a receivingunit.

The receiving unit may be configured to receive a first request sent bya first NFVO. The first request carries information about a SAP instanceassociated with a nested NS instance, and is used to request the secondNFVO to establish a nested NS instance in a composite NS instance.

The processing unit may be configured to establish, based on the SAPinstance and the information about the SAP instance, a connectionbetween the nested NS instance and the composite NS instance and aconnection between the nested NS instance and a member instance in thecomposite NS instance, and establish, based on the SAP instance and theinformation about the SAP instance, a connection relationship to amember instance in the nested NS instance.

In this application, the information about the SAP instance may includefirst information and second information. The first information may beused by the second apparatus to establish, based on the SAP instance, aconnection relationship in which the nested NS instance is connected tothe member instance in the composite NS instance through the SAPinstance. The second information may be used by the second apparatus toestablish, based on the SAP instance, a connection relationship in whichthe nested NS instance is connected to the member instance in the nestedNS instance through the SAP instance. Specifically, for specificimplementation of the SapInfo, refer to related descriptions in themethod embodiments. Details are not described herein again.

In some embodiments, the receiving unit may be further configured toreceive a second request sent by the first NFVO, where the secondrequest may be used to request to update the nested NS instance in thecomposite NS instance. Specifically, the second request carriesinformation about a SAP instance associated with the nested NS instance,and the information about the SAP instance may be used by the secondapparatus to update, based on the SAP instance, a network connectionthat is associated with the nested NS instance and that is in thecomposite NS instance. Correspondingly, the processing unit may befurther configured to update, based on the SAP instance and theinformation about the SAP instance, the network connection that isassociated with the nested NS instance and that is in the composite NSinstance.

In some embodiments, the receiving unit may be further configured toreceive a third request sent by the first NFVO, where the third requestmay be used to use an existing nested NS instance managed by the secondapparatus. Specifically, the third request carries information about aSAP instance that is of the existing nested NS instance and that isnewly added in the composite NS instance managed by the first NFVO. Theinformation about the newly added SAP instance may be used by the secondapparatus to establish, based on the newly added SAP instance, a networkconnection that is of the existing nested NS instance and that is in thecomposite NS instance. Correspondingly, the processing unit may befurther configured to establish, based on the newly added SAP instanceand the information about the newly added SAP instance, the networkconnection that is of the existing nested NS instance and that is in thecomposite NS instance.

According to a fifth aspect, this application provides an apparatus,configured to perform the network service management method in the firstaspect. The apparatus implements the consumer NFVO in the methoddescribed in the first aspect, and may include a memory, a processorcoupled to the memory, and a transceiver, where the transceiver isconfigured to communicate with another apparatus (for example, anapparatus for implementing a provider NFVO). The memory is configured tostore code for implementing the network service management methoddescribed in the first aspect. The processor is configured to executeprogram code stored in the memory, that is, perform the method providedin the first aspect or any possible implementation of the first aspect.

According to a sixth aspect, this application provides an apparatus,configured to perform the network service management method in thesecond aspect. The apparatus implements the provider NFVO in the methoddescribed in the first aspect, and may include a memory, a processorcoupled to the memory, and a transceiver, where the transceiver isconfigured to communicate with another apparatus (for example, anapparatus for implementing a consumer NFVO). The memory is configured tostore code for implementing the network service management methoddescribed in the second aspect. The processor is configured to executeprogram code stored in the memory, that is, perform the method providedin the second aspect or any possible implementation of the secondaspect.

According to a seventh aspect, this application provides an NFV MANOsystem, including a first apparatus (implementing a consumer NFVO) and asecond apparatus (implementing a provider NFVO), where the firstapparatus may be the apparatus provided in the third aspect or the fifthaspect, and the second apparatus may be the apparatus provided in thefourth aspect or the sixth aspect.

According to an eighth aspect, a computer-readable storage medium isprovided. The readable storage medium stores program code forimplementing the network service management method provided in the firstaspect or any possible implementation of the first aspect. The programcode includes an execution instruction for running the network servicemanagement method provided in the first aspect or any possibleimplementation of the first aspect.

According to a ninth aspect, a computer-readable storage medium isprovided. The readable storage medium stores program code forimplementing the network service management method provided in thesecond aspect or any possible implementation of the second aspect. Theprogram code includes an execution instruction for running the networkservice management method provided in the second aspect or any possibleimplementation of the second aspect.

According to a tenth aspect, a computer program product including aninstruction is provided. When the instruction is run on a computer, thecomputer is enabled to perform the network service management methoddescribed in the first aspect.

According to an eleventh aspect, a computer program product including aninstruction is provided. When the instruction is run on a computer, thecomputer is enabled to perform the network service management methoddescribed in the second aspect.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of thisapplication or in the background more clearly, the following brieflydescribes the accompanying drawings required for describing theembodiments of this application or the background.

FIG. 1 is a schematic diagram of an existing NFV MANO architecture;

FIG. 2 is a schematic diagram of an NFV MANO architecture in a scenarioin which a network service is provided across a plurality ofadministrative domains;

FIG. 3 is a schematic diagram of a composite network service and anested network service;

FIG. 4 is a schematic diagram of a plurality of administrative domainsand NFVOs corresponding to the plurality of administrative domains;

FIG. 5 is a schematic diagram of a hierarchical structure of a compositeNS;

FIG. 6A to FIG. 6C are schematic diagrams of existing virtual linkinformation models in a design time;

FIG. 7A to FIG. 7C are schematic diagrams, corresponding to FIG. 6A toFIG. 6C, of existing virtual link information models in a runtime;

FIG. 8A to FIG. 8C are schematic diagrams of existing virtual linkinformation models in a design time;

FIG. 9A to FIG. 9C are schematic diagrams, corresponding to FIG. 8A toFIG. 8C, of existing virtual link information models in a runtime;

FIG. 10A to FIG. 10C are schematic diagrams of virtual link informationmodels that are in a design time and that are defined from theperspective of a nested NS according to this application;

FIG. 11A to FIG. 11C are schematic diagrams, corresponding to FIG. 10Ato FIG. 10 C, of virtual link information models that are in a runtimeand that are defined from the perspective of a nested NS;

FIG. 12 is a schematic flowchart of a network service management methodaccording to this application;

FIG. 13 is an example of a schematic diagram of a network connectionestablished in a composite NS from the perspective of a nested NS;

FIG. 14 is a schematic flowchart of implementing a network servicemanagement method in an application scenario according to thisapplication;

FIG. 15 is a schematic flowchart of implementing a network servicemanagement method in another application scenario according to thisapplication;

FIG. 16 is a schematic flowchart of implementing a network servicemanagement method in still another application scenario according tothis application;

FIG. 17 is a schematic flowchart of implementing a network servicemanagement method in yet another application scenario according to thisapplication;

FIG. 18 is a schematic diagram of a structure of a network elementaccording to this application; and

FIG. 19 is a functional block diagram of an NFV MANO system and arelated apparatus according to this application.

DESCRIPTION OF EMBODIMENTS

Terms used in an implementation part of this application are merely usedto explain specific embodiments of this application, but are notintended to limit this application.

FIG. 2 shows an example of an NFV MANO architecture in a scenario inwhich a network service is provided across a plurality of administrativedomains. The scenario in which a network service is provided across aplurality of administrative domains may exist when a large serviceprovider provides a global network service (NS) through collaboration ofbranches, or when different service providers provide a lease service ofa network service (NS) by using a network sharing protocol. The globalnetwork service (NS) is also referred to as a composite network service(Composite NS). Compared with the NFV MANO architecture shown in FIG. 1,the NFV MANO architecture (which is applied to the scenario in which anetwork service is provided across a plurality of administrativedomains) shown in FIG. 2 have some changes. In FIG. 2, a consumer NFVOmanages the composite NS, and a provider NFVO manages a nested NSincluded in the composite NS. For functions and definitions ofcomponents (such as an NFVO, a VNFM, a VIM, an OSS/BSS, an EM, a VNF,and an NFVI) of the NFV MANO architecture shown in FIG. 2, refer torelated descriptions in the background. Details are not described hereinagain.

It should be noted that the NFV MANO architecture shown in FIG. 2 ismerely used to describe the technical solutions in this application moreclearly, but does not constitute a limitation on this application. Aperson of ordinary skill in the art may learn that the NFV MANOarchitecture applicable to the scenario in which a network service isprovided across a plurality of administrative domains may furtherevolve.

(1) Providing a Network Service Across a Plurality of AdministrativeDomains

One composite network service may include one or more nested networkservices, and each nested network service may be provided by anadministrative domain different from an administrative domain thatprovides the composite network service. Description is provided below indetail with reference to FIG. 3 and FIG. 4.

FIG. 3 shows an example of a composite network service and a nestednetwork service. As shown in FIG. 3, a composite network service Cprovided by an administrative domain C includes nested network servicesA and B, and the nested network services A and B are provided byadministrative domains A and B respectively. The nested network serviceA or B may also be shared by another composite network service (which isnot the composite network service C) in the administrative domain C oran administrative domain different from the administrative domain C. Theadministrative domain refers to a set of MANO management functionalentities that include one or more data centers (DC), one or more VIMsthat manage the data centers, and one or more VNFMs (including all VNFsmanaged by the VNFMs). Each administrative domain includes one NFVO,configured to provide a specific group of network services in theadministrative domain.

FIG. 4 shows an example of a plurality of administrative domains. Eachadministrative domain provides one group of network services. An NFVO-1in the administrative domain C is at a top layer, which means that theNFVO-1 manages the composite network service C. An NFVO-2 in theadministrative domain A and an NFVO-3 in the administrative domain Bmanage the nested network services A and B respectively, and expose thenested network services to the NFVO-1 in the administrative domain C.Herein, different NFVOs may interact with each other through a referencepoint (reference point) Or-Or.

Specifically, concepts of a composite NS and a nested NS are proposedfor a hierarchical structure of an NS instance. As shown in FIG. 5, acomposite NS instance may be usually represented as a tree-likehierarchical structure, and an NS instance located at the top of thehierarchical structure (a root node of the tree-like structure) isreferred to as a composite NS instance. Member instances in onecomposite NS instance may include one or more nested NS instances, andmay further include one or more VNF instances or PNF instances. In thecomposite NS instance, the nested NS instance, the VNF instance, and thePNF instance are at a same hierarchical level. Member instances in onenested NS instance may include one or more VNF instances or PNFinstances. Optionally, a member instance in one nested NS instance mayinclude a sub-nested NS instance.

An example is used for describing the concepts of the composite NS andthe nested NS. To implement a virtualized evolved packet core (EvolvedPacket Core, EPC) network service, member VNF instances may be used toconstitute several nested NS instances. For example, a vMME function, acontrol plane function of a vSGW, and a control plane function of a vPGWare used to constitute a vEPC control plane network service. A userplane function of the vSGW and a user plane function the vPGW are usedto constitute a vEPC user plane (or forwarding plane) network service.Policy control-related functions, such as a vPCRF, vTDF, and vSCEF, areused to constitute a vEPC policy control network service. In theapplication, the vEPC is a composite NS, and the vEPC control planenetwork service, the vEPC user plane (or forwarding plane) networkservice, and the vEPC policy control network service are nested NSs.

Further, how to provide a vEPC network service by a telecom operatorhaving an ultra-large quantity of users is considered. Assuming that anetwork of the telecom operator has a two-level structure: a groupcompany network and a plurality of provincial subsidiary networks, eachlevel of the network has an administrative domain for the level of thenetwork, and is configured with one NFVO. In this scenario, an NFVO inthe group company network may be considered as a consumer NFVO (anNFVO-1), and an NFVO in each of the provincial subsidiary networks maybe considered as a provider NFVO (an NFVO-2). When the telecom operatordetermines to provide the vEPC network service at a level of the groupcompany network, the telecom operator may specify that a vEPC controlplane network service is provided by a Guangdong provincial subsidiarynetwork, a vEPC user plane network service is provided by a Jiangsuprovincial subsidiary network, and a vEPC policy control network serviceis provided by a Zhejiang provincial subsidiary network.

In a scenario in which a network service is provided across a pluralityof administrative domains, the composite NS and the nested NS arelocated in different administrative domains, and life cycle managementfor the composite NS and the nested NS is performed by NFVOs (includingthe consumer NFVO and one or more provider NFVOs) in differentadministrative domains.

(2) Virtual Link Information Model of a Network Service

The following separately describes, from the perspective of a designtime and a runtime, a virtual link information model defined in anexisting ETSI NFV standard.

FIG. 6A to FIG. 6C shows virtual link information models used to connectmember instances in a network service.

As shown in FIG. 6A, the virtual link (VL) information model is definedstarting from an association relationship between descriptors(Descriptor) in the design time. A virtual link descriptor is aninformation model template to which a reference needs to be made when avirtual link is instantiated, and includes a static attribute of avirtual link instance before the virtual link instance is created. Inthe design time, a network service descriptor (NSD) needs to indicate: aVNF descriptor (VNFD) and/or a PNF descriptor (PNFD) that are/isassociated with the virtual link descriptor, a specific VNF externalconnection point descriptor (VnfExtCpd) used to associate the virtuallink descriptor with a corresponding VNFD, and/or a specific PNFexternal connection point descriptor (PnfExtCpd) used to associate thevirtual link descriptor with a corresponding PNFD.

As shown in FIG. 6B, after entering the runtime, the virtual linkinstance is created with reference to the virtual link descriptor.Specifically, with reference to the virtual link descriptor, the virtuallink instance is associated with a specific VNF instance (whichindicates that the virtual link instance is connected to the VNFinstance), and/or the virtual link instance is associated with aspecific PNF instance (which indicates that the virtual link instance isconnected to the PNF instance). An association relationship between thevirtual link instance and the VNF instance (or the PNF instance) isestablished by configuring an association between an external connectionpoint VnfExtCp instance (or a PnfExtCp instance) of the VNF instance (orthe PNF instance) and a port NsLinkPort of the virtual link instance.The virtual link instance in the runtime is finally mapped to acorresponding virtual network resource at an NFVI layer, and isconnected, through a network link at a layer 2 (layer 2, L2) or layer 3(layer 3, L3), to a configured virtual port of a VNF instance of avirtualized computing and storage resource or a configured virtual portof a PNF instance. Reference may be made to FIG. 6C.

FIG. 7A to FIG. 7C shows how a virtual link is used to connect a memberinstance of a network service to a service access point (SAP) of thenetwork service.

Similarly, as shown in FIG. 7A, in the design time, the following needsto be indicated: a VNFD (or a PNFD) and a service access pointdescriptor (SAP descriptor, SAPD) that are associated with a virtuallink descriptor, and a specific VNF external connection point descriptor(VnfExtCpd) or PNF external connection point descriptor (PnfExtCpd) thatis used to associate the virtual link descriptor with a correspondingSAPD.

As shown in FIG. 7B, after entering the runtime, a virtual link instanceis associated with a specific VNF instance (or a specific PNF instance)and a specific SAP instance with reference to the virtual linkdescriptor. It indicates that the virtual link instance is connected tothe VNF instance (or the PNF instance) and the SAP instance. The virtuallink instance in the runtime is finally mapped to a correspondingvirtual network resource at an NFVI layer, and is connected, through anetwork link at a layer 2 (layer 2, L2) or layer 3 (layer 3, L3), to aconfigured virtual port of a VNF instance of a virtualized computing andstorage resource or a configured virtual port of a PNF instance, and aconfigured virtual port of a SAP instance. Reference may be made to FIG.7C.

The design time mentioned in this application refers to a phase in whichan association relationship between various descriptors (such as anetwork service descriptor, a VNF descriptor, a PNF descriptor, avirtual link descriptor, and an external connection point descriptor) isdefined before instantiation of a network service or establishment of anetwork connection. The runtime mentioned in this application refers toa phase, during or after the instantiation of the network service or theestablishment of the network connection, in which an associationrelationship between instances (such as a network service instance, aVNF instance, a PNF instance, a virtual link instance, and an externalconnection point instance) is set based on the association relationshipbetween various descriptors defined in the design time. It should beunderstood that each instance is created or updated with reference to adescriptor file corresponding to the instance.

It can be learned from the foregoing that the virtual link informationmodel defined in the existing ETSI NFV standard mainly describes aconnection to the VNF instances and/or the PNF instance in an NSinstance and a connection between a SAP of the NS instance and the VNFinstance and/or the PNF instance from the perspective that a consumerNFVO performs network connection. However, there is no virtual linkinformation model defined from the perspective of a nested NS instance.

In addition, in a scenario in which an NS is provided across a pluralityof administrative domains, there may be a requirement of informationisolation between different administrative domains. For example, a VNFexternal connection point descriptor (VnfExtCpd) in an administrativedomain corresponding to a consumer NFVO is invisible to a provider NFVO.Similarly, a VNF external connection point descriptor (VnfExtCpd) in anadministrative domain corresponding to the provider NFVO is invisible tothe consumer NFVO. However, a topology structure described in thevirtual link information model defined in the existing ETSI NFV standardis visible to the outside. Therefore, the virtual link information modeldefined in the existing ETSI NFV standard cannot meet the requirement ofinformation isolation between different administrative domains.

This application provides a network service management method in which avirtual link information model is defined from the perspective of anested NS instance. In this way, the nested NS instance can beexternally connected to a composite NS instance and each member instancein the composite NS instance through a virtual link, and can beinternally connected to each member instance in the nested NS instancethrough a virtual link.

In this application, the virtual link information model defined from theperspective of the nested NS instance may include two parts: an externalvirtual link information model and an internal virtual link informationmodel.

(1) External virtual link information model: The nested NS instance maybe connected, based on a SAP instance of the nested NS instance, to anexternal link point of another member instance in the composite NSinstance through an external virtual link. For example, the externallink point of the another member instance is an external connectionpoint VnfExtCp of a VNF instance, an external connection point PnfExtCpof a PNF instance, or a service access point SAP of another nested NSinstance. The nested NS instance may be further connected, based on theSAP instance of the nested NS instance, to a SAP instance of thecomposite NS instance through an external virtual link. In other words,an external virtual link instance may be used to externally connect thenested NS instance to a member instance in the composite NS instancebased on the SAP instance of the nested NS instance.

(2) Internal virtual link information model: The nested NS instance isconnected, based on a SAP instance of the nested NS instance, to anexternal link point of a member instance in the nested instance throughan internal virtual link. For example, the external link point of themember instance is an external connection point VnfExtCp of a VNFinstance, an external connection point PnfExtCp of a PNF instance, or aservice access point SAP of a sub-nested NS instance. In other words, aninternal virtual link instance may be used to internally connect thenested NS instance to the member instance in the nested NS instancebased on the SAP instance of the nested NS instance.

First, the external virtual link information model is described.

FIG. 8A to FIG. 8C show examples of external virtual link informationmodels in a design time. The external virtual link information model inthe design time is mainly used to indicate an association relationshipbetween descriptors, to provide a reference for a connectionrelationship related to subsequent instantiation of an external virtuallink.

As shown in FIG. 8A, a nested network service descriptor Nested NSD #1is associated with an external virtual link descriptor NSVirtualLinkDesc#1 and a descriptor VNFD #2 of a VNF in a composite network service.Specifically, the NSVirtualLinkDesc #1 is associated with the Nested NSD#1 by using SAP descriptors Sapd #1.1 and Sapd #1.2, and is associatedwith the VNFD #2 by using an external connection point descriptorPnfExtCp #2.1.

As shown in FIG. 8B, a nested network service descriptor Nested NSD #1is associated with an external virtual link descriptor NSVirtualLinkDesc#1 and a descriptor Nested NSD #2 of another nested network service in acomposite network service. Specifically, the NSVirtualLinkDesc #1 isassociated with the Nested NSD #1 by using SAP descriptors Sapd #1.1 andSapd #1.2, and is associated with the Nested NSD #2 by using serviceaccess point descriptors Sapd #2.1 and Sapd #2.2.

As shown in FIG. 8C, a nested network service descriptor Nested NSD #1is associated with an external virtual link descriptor NSVirtualLinkDesc#1 and a descriptor Sapd #2 of a service access point of a compositenetwork service.

FIG. 9A to FIG. 9C show examples of external virtual link informationmodels that are in a runtime and based on a SAP of a nested NS. Theexternal virtual link information model in the runtime is mainly used toindicate an association relationship between instances, and is used toestablish a connection between the instances. After the instances enterthe runtime, the external virtual link information models in the runtimeshown in FIG. 9A to FIG. 9C are respectively created with reference tothe external virtual link information models in the design time shown inFIG. 8A to FIG. 8C.

As shown in FIG. 9A, a nested NS instance Nested NS #1 is connected,based on service access points Sap #1.1 and Sap #1.2 of the nested NSinstance Nested NS #1, to an external link point VnfExtCp #2.1 of a VNFinstance VNF #2 in a composite NS instance through an external virtuallink instance NSVirtualLink #1. Specifically, the NSVirtualLink #1 isconnected to the Sap #1.1 through a port instance NsLinkPort #1.1, isconnected to the Sap #1.2 through a port instance NsLinkPort #1.2, andis connected to the VnfExtCp #2.1 through a port instance NsLinkPort#1.3. It can be learned that connections indicated by the externalvirtual link information model in FIG. 9A are established with referenceto the external virtual link information model in the design time inFIG. 8A.

As shown in FIG. 9B, a nested NS instance Nested NS #1 is connected,based on service access points Sap #1.1 and Sap #1.2 of the nested NSinstance Nested NS #1, to a service access point Sap #2.1 of anothernested NS instance Nested NS #2 in a composite NS instance through anexternal virtual link instance NSVirtualLink #1. Specifically, theNSVirtualLink #1 is connected to the Sap #1.1 through a port instanceNsLinkPort #1.1, is connected to the Sap #1.2 through a port instanceNsLinkPort #1.2, and is connected to the Sap #2.1 through a portinstance NsLinkPort #1.3. It can be learned that connections indicatedby the external virtual link information model in FIG. 9B areestablished with reference to the virtual link information model in thedesign time in FIG. 8B.

As shown in FIG. 9C, a nested NS instance Nested NS #1 is connected,based on a service access point Sap #1.1 of the nested NS instanceNested NS #1, to a service access point Sap #1 of a composite NSinstance through an external virtual link instance NSVirtualLink #1.Specifically, the NSVirtualLink #1 is connected to the Sap #1.1 througha port instance NsLinkPort #1.1. It can be learned that a connectionindicated by the external virtual link information model in FIG. 9C isestablished with reference to the virtual link information model in thedesign time in FIG. 8C.

The examples shown in FIG. 8A to FIG. 8C and FIG. 9A to FIG. 9C aremerely used to explain this application, but shall not constitute alimitation.

Then, the internal virtual link information model is described.

FIG. 10A to FIG. 10C show examples of internal virtual link informationmodels in a design time. The internal virtual link information model inthe design time is mainly used to indicate an association relationshipbetween descriptors, to provide a reference for a connectionrelationship related to subsequent instantiation of an internal virtuallink.

As shown in FIG. 10A, a descriptor Sub-Nested NSD #1 of a sub-nested NSin a nested NS is associated with an internal virtual link descriptorNSVirtualLinkDesc #1 and a descriptor Sapd #2 of a SAP of the nested NS.Specifically, the NSVirtualLinkDesc #1 is associated with the Sub-NestedNSD #1 by using a SAP descriptor Sapd #1.1.

As shown in FIG. 10B, a descriptor VNFD #1 of a VNF in a nested NS isassociated with an internal virtual link descriptor NSVirtualLinkDesc #1and a descriptor Sapd #2 of a SAP of the nested NS. Specifically, theNSVirtualLinkDesc #1 is associated with the VNFD #1 by using an externalconnection point descriptor VnfExtCpd #1.1.

As shown in FIG. 10C, a descriptor PNFD #1 of a PNF in a nested NS isassociated with an internal virtual link descriptor NSVirtualLinkDesc #1and a descriptor Sapd #2 of a SAP of the nested NS. Specifically, theNSVirtualLinkDesc #1 is associated with the PNFD #1 by using an externalconnection point descriptor VnfExtCpd #1.1.

FIG. 11A to FIG. 11C show examples of internal virtual link informationmodels that are in a runtime and based on a SAP of a nested NS. Theinternal virtual link information model in the runtime is mainly used toindicate an association relationship between instances, and is used toestablish a connection between the instances. After the instances enterthe runtime, the internal virtual link information models in the runtimeshown in FIG. 11A to FIG. 11C are respectively created with reference tothe internal virtual link information models in the design time shown inFIG. 10A to FIG. 10C.

As shown in FIG. 11A, a sub-nested NS instance Sub-Nested NS #1 isconnected, based on a service access point Sap #1.1 of the sub-nested NSinstance Sub-Nested NS #1, to a service access point instance Sap #1 ofa nested NS instance through an internal virtual link instanceNSVirtualLink #1. Specifically, the NSVirtualLink #1 is connected to theSap #1.1 through a port instance NsLinkPort #1.1, and is connected tothe Sap #1 through a port instance NsLinkPort #1.3. It can be learnedthat a connection indicated by the internal virtual link informationmodel in FIG. 11A is established with reference to the virtual linkinformation model in the design time in FIG. 10A.

As shown in FIG. 11B, a VNF instance VNF #1 is connected, based on anexternal connection point VnfExtCp #1.1 of the VNF instance VNF #1, to aservice access point instance Sap #1 of a nested NS instance through aninternal virtual link instance NSVirtualLink #1. Specifically, theNSVirtualLink #1 is connected to the VnfExtCp #1.1 through a portinstance NsLinkPort #1.1, and is connected to the Sap #1 through a portinstance NsLinkPort #1.3. It can be learned that a connection indicatedby the internal virtual link information model in FIG. 11B isestablished with reference to the virtual link information model in thedesign time in FIG. 10B.

As shown in FIG. 11C, a PNF instance PNF #1 is connected, based on anexternal connection point PnfExtCp #1.1 of the PNF instance PNF #1, to aservice access point instance Sap #1 of a nested NS instance through aninternal virtual link instance NSVirtualLink #1. Specifically, theNSVirtualLink #1 is connected to the PnfExtCp #1.1 through a portinstance NsLinkPort #1.1, and is connected to the Sap #1 through a portinstance NsLinkPort #1.3. It can be learned that a connection indicatedby the internal virtual link information model in FIG. 11C isestablished with reference to the virtual link information model in thedesign time in FIG. 10C.

The examples shown in FIG. 10A to FIG. 10C and FIG. 11A to FIG. 11C aremerely used to explain this application, but shall not constitute alimitation.

It may be understood that virtual link information models defined inthis application are designed from the perspective of the nested NSinstance, and can better meet a requirement for describing a networkconnection from the perspective of a nested NS. For example, for aconsumer NFVO (NFVO-1) and a provider NFVO (NFVO-2), a virtual linkneeds to be used to establish a connection between a nested NS instancemanaged by the NFVO-2 and the composite NS instance managed by theNFVO-1.

In some optional embodiments, a peer connection point, such as a SAP ofa sub-nested NS, an external connection point VnfExtCp of a VNF, or anexternal connection point PnfExtCp of a PNF, that is connected to thenested NS through an internal virtual link may be invisible to theconsumer NFVO. In other words, information about the peer connectionpoint may not be reflected in the virtual link information model. Thisfurther meets a requirement of information isolation between differentadministrative domains.

Based on the virtual link information model defined in this application,the provider NFVO that manages the nested NS may establish a connectionindicated by the virtual link information model. With reference to FIG.12, the following describes an overall procedure of a network servicemanagement method provided in this application. Details are as follows.

S101: A first NFVO sends a first request to a second NFVO. Herein, thefirst NFVO may be a consumer NFVO that manages a composite NS instance,and the second NFVO may be a provider NFVO that manages a nested NSinstance. Specifically, the first request may be used to request tocreate the nested NS instance in the composite NS instance and carriesinformation about a SAP instance associated with the nested NS instance.

Herein, the information about the SAP instance is specifically used todescribe a virtual link information model associated with the SAPinstance, and may be used by the second NFVO to establish connectionsindicated by the virtual link information model, to be specific,establish a connection between the nested NS instance and the compositeNS instance that is externally connected to the nested NS instance basedon the SAP instance and a connection between the nested NS instance anda member instance that is in the composite NS instance and that isexternally connected to the nested NS instance based on the SAPinstance, and establish a connection between the nested NS instance anda member instance that is in the nested NS instance and that isinternally connected to the nested NS instance based on the SAPinstance.

S102 and S103: Correspondingly, the second NFVO receives the firstrequest sent by the first NFVO, and in response to the first request,the second NFVO may perform a procedure of creating the nested NSinstance and then return an instance creation success response to thefirst NFVO. The response may carry an identifier of the created nestedNS instance.

S104 and S105: The second NFVO may establish, based on the information(which is briefly referred to as SapInfo below) that is about the SAPinstance associated with the nested NS instance and that is carried inthe first request, the connection between the nested NS instance and thecomposite NS instance that is externally connected to the nested NSinstance through the SAP instance and the connection between the nestedNS instance and the member instance that is in the composite NS instanceand that is externally connected to the nested NS instance through theSAP instance, and establish the connection between the nested NSinstance and the member instance that is in the nested NS instance andthat is internally connected to the nested NS instance through the SAPinstance; and then the second NFVO may return a connection establishmentcomplete response to the first NFVO. Optionally, the connectionestablishment complete response may alternatively be combined into theforegoing instance creation success response. In other words, the secondNFVO may return the connection establishment complete response to thefirst NFVO implicitly, that is, use the instance creation successresponse to indicate that connection establishment is completed.

It may be understood that, the SapInfo is carried in a request (namely,the first request) used to create the nested NS instance, to indicatethe provider NFVO to establish external and internal network connectionsof the nested NS instance based on the SapInfo from the perspective ofthe nested NS instance. This can meet a requirement for establishing anetwork connection from the perspective of a nested NS.

The following describes specific implementation of the SapInfo indetail.

In this application, the SapInfo may include two parts: firstinformation and second information. The first information isspecifically used to describe an external virtual link informationmodel, and may be used by the second NFVO to establish a connectionbetween the nested NS instance and a member instance that is in thecomposite NS instance and that is (externally) connected to the nestedNS instance through the SAP instance. The second information isspecifically used to describe an internal virtual link informationmodel, and may be used by the second NFVO to establish a connectionbetween the nested NS instance and a member instance that is in thenested NS instance and that is (internally) connected to the nested NSinstance through the SAP instance.

In this application, the first information may include an identifier ofan external virtual link instance, an identifier of a port through whichthe SAP instance is connected to the external virtual link instance, andan identifier of a peer connection point connected to the SAP instancethrough the external virtual link instance. The peer connection pointconnected to the SAP instance through the external virtual link instancemay be an external connection point that is of the member instance inthe composite network service instance and that is connected to the SAPinstance through the external virtual link instance. For example, theexternal connection point is an external connection point VnfExtCp of aVNF instance, an external connection point PnfExtCp of a PNF instance,or a service access point SAP of another nested NS instance. The peerconnection point connected to the SAP instance through the externalvirtual link instance may alternatively be a service access point SAP ofthe composite NS instance.

In this application, the second information may include an identifier ofan internal virtual link instance, a port through which the SAP instanceis connected to the internal virtual link instance, and an identifier ofa peer connection point connected to the SAP instance through theinternal virtual link instance. The peer connection point connected tothe SAP instance through the internal virtual link instance may be anexternal connection point that is of the member instance in the nestednetwork service instance and that is connected to the SAP instancethrough the internal virtual link instance. For example, the externalconnection point is an external connection point VnfExtCp of a VNFinstance, an external connection point PnfExtCp of a PNF instance, or aservice access point SAP of a sub-nested NS instance.

Information about the peer connection point may not be reflected in theinternal virtual link information model, to ensure information isolationbetween different administrative domains. To be specific, the secondinformation may optionally include an identifier of a second virtuallink instance and a port through which the SAP instance is connected tothe internal virtual link instance, but does not include an identifierof a peer connection point connected to the SAP instance through theinternal virtual link instance. In other words, an internal peerconnection point that is internally connected to the nested NS instancethrough the SAP instance is invisible to the outside (that is, thecomposite NS instance and another member instance in the composite NSinstance).

For example, Table 1 to Table 3 show an example of an implementation ofthe SapInfo.

TABLE 1 Attribute Qualifier Cardinality Content Description SAP instanceMandatory 1 Identifier Identifier of the identifier SAP instance, whichcan be used to identify the SapInfo SAPD Mandatory 1 Identifier SAPDidentifier identifier used for SAP instantiation SAP name Mandatory 1String Human-readable SAP name Description Mandatory 1 StringHuman-readable SAP description Address Mandatory 1 Not SAP address,assigned which can be provided by an NFVO Internal Mandatory 1 InternalTopology link association association internally associated with a SAPthrough a virtual link External Mandatory 1 External Topology linkassociation association externally associated with a SAP through avatual link

Table 2 shows an example of the internal association in Table 1 (whichmeets the requirement of information isolation between differentadministrative domains). Details are as follows:

TABLE 2 Attribute Qualifier Cardinality Content Description attributequalifier cardinality content description Internal Mandatory 1Identifier Identifier of an virtual link ID internal virtual instancelink identifier Internal Mandatory 1 Identifier Port through winch linkport ID a SAP is connected to the internal virtual link

Table 3 shows an example of the external association (ExternalAssociation) in Table 1. Details are as follows:

TABLE 3 Attribute Qualifier Cardinality Content Description attributequalifier cardinality content description External Mandatory 1Identifier Identifier of an virtual link ID external virtual instancelink identifier External Mandatory 1 Identifier Port through which linkport ID a SAP is connected to the external virtual link Peer Mandatory 1Identifier Peer connection connection ID point connected to point theSAP through the external virtual link

With reference to Table 1 to Table 3, Table 1 shows content included inthe SapInfo, where the internal association is the second information,and the external association is the first information. Table 2 showscontent included in the internal association, and the information aboutthe peer connection point is not reflected herein, that is, the internalpeer connection point is invisible to the outside. Table 3 shows contentincluded in the external association. The peer connection point may bethe external connection point VnfExtCp of the VNF instance in thecomposite NS instance, the external connection point PnfExtCp of the PNFinstance, or the service access point SAP of the another nested NSinstance. The peer connection point may alternatively be the serviceaccess point SAP of the composite NS instance.

If all member instances in the composite NS instance are available(available), the second NFVO that manages the nested NS may establish,based on the virtual link information model, connections indicated bythe virtual link information model. Herein, all the member instances inthe composite NS instance may include all nested NS instances, all VNFinstances, and all PNF instances in the composite NS instance.

1. In this application, the second NFVO may establish, based on the SAPinstance of the nested NS instance, connections indicated by theexternal virtual link information model in at least one of the followingmanners:

Manner 1: The second NFVO establishes, based on the first information inthe SapInfo, a connection between the SAP instance and a SAP instancethat is of the composite NS instance and that is externally connected tothe SAP instance through the external virtual link instance.

Manner 2: The second NFVO establishes, based on the first information inthe SapInfo, a connection between the SAP instance and a SAP instancethat is of a nested NS instance in the composite NS instance and that isexternally connected to the SAP instance through the external virtuallink instance.

Manner 3: The second NFVO establishes, based on the first information inthe SapInfo, a connection between the SAP instance and the externalconnection point that is of the VNF instance in the composite NSinstance and that is externally connected to the SAP instance throughthe external virtual link instance.

Manner 4: The second NFVO establishes, based on the first information inthe SapInfo, a connection between the SAP instance and the externalconnection point that is of the PNF instance in the composite NSinstance and that is externally connected to the SAP instance throughthe external virtual link instance.

2. In this application, the second NFVO may establish, based on the SAPinstance of the nested NS instance, connections indicated by theinternal virtual link information model in at least one of the followingmanners:

Manner 1: The second NFVO establishes, based on the second informationin the SapInfo, a connection between the SAP instance and a SAP instancethat is of a sub-nested NS instance in the nested NS instance and thatis internally connected to the SAP instance through the internal virtuallink instance.

Manner 2: The second NFVO establishes, based on the second informationin the SapInfo, a connection between the SAP instance and the externalconnection point that is of the VNF instance in the nested NS instanceand that is internally connected to the SAP instance through theinternal virtual link instance.

Manner 3: The second NFVO establishes, based on the second informationin the SapInfo, a connection between the SAP instance and the externalconnection point that is of the PNF instance in the nested NS instanceand that is internally connected to the SAP instance through theinternal virtual link instance.

With reference to FIG. 13, the following describes in detail the SapInfoand how the second NFVO establishes, based on the SapInfo, connectionsindicated by the virtual link information model described by theSapInfo. It is assumed that the first NFVO manages a composite NSinstance in FIG. 13, and the second NFVO manages a nested NS #2 in FIG.13. In addition, the first request carries information (that is,SapInfo) about a SAP instance associated with the nested NS #2.

I. SapInfo Associated with the Nested NS #2

As shown in FIG. 13, the SapInfo associated with the nested NS #2includes information about a SAP #2.1, information about a SAP #2.2, andinformation about a SAP #2.3.

(1) The information about the SAP #2.1 is used to describe a virtuallink information model associated with the SAP #2.1, to be specific, aninternal virtual link (VL #2) information model and an external virtuallink (VL #4) information model. The SAP #2.1 is externally connected toa VNF #2 through the external virtual link (VL #4), and is internallyconnected to a PNF #1 through the internal virtual link (VL #2).

Specifically, the information about the SAP #2.1 may include firstinformation and second information. The first information may include anidentifier of the VL #4, an identifier of a port (not shown in thefigure) through which the SAP #2.1 is externally connected to anexternal peer connection point through the VL #4, and an identifier ofthe external peer connection point (to be specific, an externalconnection point VnfExtCP #2.1 of the VNF #2) connected to the SAP #2.1through the VL #4. The second information may include an identifier ofthe VL #2 and identifiers of ports (not shown in the figure) throughwhich the SAP #2.1 is internally connected to internal peer connectionpoints through the VL #2. Optionally, identifiers of the internal peerconnection points, to be specific, identifiers of external link pointsPnfExtCP #1.1 and PnfExtCP #1.2 of the PNF #1, may be included in thesecond information, or may not be included in the second information.When there is a requirement of information isolation between differentadministrative domains, the identifiers of the internal peer connectionpoints are not included in the second information.

(2) The information about the SAP #2.2 is used to describe a virtuallink information model associated with the SAP #2.2, to be specific, aninternal virtual link (VL #3) information model and an external virtuallink (VL #5) information model. The SAP #2.2 is externally connected toa nested NS #3 through the external virtual link (VL #5), and isinternally connected to a sub-nested NS #1 through the internal virtuallink (VL #3).

Specifically, the information about the SAP #2.2 may include firstinformation and second information. The first information may include anidentifier of the VL #5, an identifier of a port (not shown in thefigure) through which the SAP #2.2 is externally connected to anexternal peer connection point through the VL #5, and an identifier ofthe external peer connection point (to be specific, a service accesspoint SAP #3.1 of the nested NS #3) connected to the SAP #2.2 throughthe VL #5. The second information may include an identifier of the VL #3and an identifier of a port (not shown in the figure) through which theSAP #2.2 is internally connected to an internal peer connection pointthrough the VL #3. Optionally, an identifier of the internal peerconnection point, to be specific, an identifier of a service accesspoint SAP #1.1 of the sub-nested NS #1, may be included in the secondinformation, or may not be included in the second information. Whenthere is a requirement of information isolation between differentadministrative domains, the identifier of the internal peer connectionpoint is not included in the second information.

(3) The information about the SAP #2.3 is used to describe a virtuallink information model associated with the SAP #2.3, to be specific, aninternal virtual link (VL #1) information model and an external virtuallink (VL #6) information model. The SAP #2.3 is externally connected tothe composite NS instance through the external virtual link (VL #6), andis internally connected to a VNF #1 through the internal virtual link(VL #1).

Specifically, the information about the SAP #2.3 may include firstinformation and second information. The first information may include anidentifier of the VL #6, an identifier of a port (not shown in thefigure) through which the SAP #2.3 is externally connected to anexternal peer connection point through the VL #6, and an identifier ofthe external peer connection point (to be specific, a service accesspoint SAP #5.1 of the composite NS instance) connected to the SAP #2.3through the VL #6. The second information may include an identifier ofthe VL #1 and identifiers of ports (not shown in the figure) throughwhich the SAP #2.3 is internally connected to internal peer connectionpoints through the VL #1. Optionally, identifiers of the internal peerconnection points, to be specific, identifiers of external connectionpoints VnfExtCP #1.1 and VnfExtCP #1.2 of the VNF #1, may be included inthe second information, or may not be included in the secondinformation. When there is a requirement of information isolationbetween different administrative domains, the identifiers of theinternal peer connection points are not included in the secondinformation.

II. The second NFVO establishes, based on the SapInfo, the connectionsindicated by the virtual link information model described by theSapInfo.

(1) Specifically, a manner in which the second NFVO establishesconnections based on the information about the SAP #2.1 may include thefollowing steps:

1. The second NFVO may establish, based on the first information in theinformation about the SAP #2.1, a connection between the SAP #2.1 andthe external connection point VnfExtCP #2.1 that is of the VNF #2 in thecomposite NS instance and that is externally connected to the SAP #2.1through the VL #4.

2. The second NFVO may establish, based on the second information in theinformation about the SAP #2.1, connections between the SAP #2.1 and theexternal connection points PnfExtCP #1.1 and PnfExtCP #1.2 that are ofthe PNF #1 in the nested NS #2 and that are internally connected to theSAP #2.1 through the VL #2. Optionally, when the second information doesnot include the identifiers of the PnfExtCP #1.1 and the PnfExtCP #1.2,the second NFVO may independently determine, according to a presetpolicy, internal peer connection points that are to be internallyconnected to the SAP #2.1 through the VL #2. For example, the secondNFVO may select, based on a service type, internal peer connectionpoints that are to be internally connected to the VL #2. Service typesassociated with the selected internal peer connection points areresponsible are the same as a service type associated with the VnfExtCP#2.1 that is connected to the SAP #2.1 through the VL #4. The example ismerely used to explain this application, and shall not constitute alimitation.

(2) Specifically, a manner in which the second NFVO may establishconnections based on the information about the SAP #2.2 may include thefollowing steps:

1. The second NFVO may establish, based on the first information in theinformation about the SAP #2.2, a connection between the SAP #2.2 andthe service access point SAP #3.1 that is of the nested NS #3 in thecomposite NS instance and that is externally connected to the SAP #2.2through the VL #5.

2. The second NFVO may establish, based on the second information in theinformation about the SAP #2.2, a connection between the SAP #2.2 andthe service access point SAP #1.1 that is of the sub-nested NS #1 in thenested NS #2 and that is internally connected to the SAP #2.2 throughthe VL #3. Optionally, when the second information does not include theidentifier of the SAP #1.1, the second NFVO may independently determine,according to a preset policy, an internal peer connection point that isto be internally connected to the SAP #2.2 through the VL #3. Forexample, the second NFVO may select, based on a service type, aninternal peer connection point that is to be internally connected to theVL #3. A service type associated with the selected internal peerconnection point is the same as a service type associated with the SAP#3.1 that is connected to the SAP #2.2 through the VL #5. The example ismerely used to explain this application, and shall not constitute alimitation.

(3) Specifically, a manner in which the second NFVO may establishconnections based on the information about the SAP #2.3 may include thefollowing steps:

1. The second NFVO may establish, based on the first information in theinformation about the SAP #2.3, a connection between the SAP #2.3 andthe service access point SAP #5.1 that is of the composite NS instanceand that is externally connected to the SAP #2.3 through the VL #6.

2. The second NFVO may establish, based on the second information in theinformation about the SAP #2.3, connections between the SAP #2.3 and theexternal connection points VnfExtCP #1.1 and VnfExtCP #1.2 that are ofthe VNF #1 in the nested NS #2 and that are internally connected to theSAP #2.3 through the VL #1. Optionally, when the second information doesnot include the identifiers of the VnfExtCP #1.1 and the VnfExtCP #1.2,the second NFVO may independently determine, according to a presetpolicy, internal peer connection points that are internally connected tothe SAP #2.3 through the VL #1. For example, the second NFVO may select,based on a service type, internal peer connection points that areinternally connected to the VL #3. Service types associated with theselected internal peer connection points are the same as a service typeassociated with the SAP #5.1. The example is merely used to explain thisapplication, and shall not constitute a limitation.

Similarly, for the second NFVO that manages the nested NS #3 in theexamples in FIG. 13, SapInfo associated with the nested NS #3 includesinformation about the SAP #3.1, information about a SAP #3.2, andinformation about a SAP #3.3. The second NFVO that manages the nested NS#3 may establish, based on the SapInfo associated with the nested NS #3,connections indicated by a virtual link information model described bythe SapInfo. For details, refer to the examples in FIG. 13, and detailsare not described herein again.

In this application, an external virtual link may be referred to as afirst virtual link, and an internal virtual link may be referred to as asecond virtual link.

Further, as shown in FIG. 12, the first NFVO may initiate, to the secondNFVO, a process of updating the nested NS instance, for example, addinga service access point or modifying a service access point, to indicatethe second NFVO to update a network connection associated with thenested NS instance. Details are as follows.

S106. The first NFVO sends a second request to the second NFVO.Specifically, the second request may be used to request to update thenested NS instance in the composite NS instance. Optionally, the secondrequest may further include an NS update type, for example, adding aservice access point or modifying a service access point. Specifically,the second request may carry the SapInfo associated with the nested NSinstance.

Herein, the SapInfo is specifically used to describe a virtual linkinformation model associated with the SAP instance, and may be used bythe second NFVO to update network connections associated with the nestedNS instance, to be specific, update the connection between the nested NSinstance and the composite NS instance that is externally connected tothe nested NS instance based on the SAP instance and the connectionbetween the nested NS instance and the member instance that is in thecomposite NS instance and that is externally connected to the nested NSinstance based on the SAP instance, or update the connection between thenested NS instance and the member instance that is in the nested NSinstance and that is internally connected to the nested NS instancebased on the SAP instance. For specific implementation of the SapInfo,refer to related descriptions in S101 to S105. Details are not describedherein again.

S107 and S108: Correspondingly, the second NFVO receives the secondrequest sent by the first NFVO, and in response to the second request,the second NFVO may perform a procedure of updating the nested NSinstance and then return an instance update success response to thefirst NFVO.

S109 and S110: The second NFVO may update, based on the SapInfo that isassociated with the nested NS instance and that is carried in the secondrequest, the connection between the nested NS instance and the compositeNS instance that is externally connected to the nested NS instance basedon the SAP instance and the connection between the nested NS instanceand the member instance that is in the composite NS instance and that isexternally connected to the nested NS instance based on the SAPinstance, or update the connection between the nested NS instance andthe member instance that is in the nested NS instance and that isinternally connected to the nested NS instance based on the SAPinstance. Then, the second NFVO may return a connection update successresponse to the first NFVO.

Specifically, updating of the network connections associated with thenested NS instance may include at least one of the following:establishing a new network connection associated with the nested NSinstance, modifying an existing network connection associated with thenested NS instance, or removing an existing network connectionassociated with the nested NS instance.

For example, in the examples in FIG. 13, for the second NFVO thatmanages the nested NS #2, it is assumed that the NS update type includedin the second request is adding a SAP instance, and SapInfo included inthe second request is information about a “SAP #2.4” (not shown). Inthis case, the second NFVO may establish, based on the information aboutthe SAP #2.4, external connection and internal connections that are ofthe nested NS #2 and that are based on the SAP #2.4, in other words,establish new network connections associated with the nested NSinstance.

For another example, in the examples in FIG. 13, for the second NFVOthat manages the nested NS #2, it is assumed that the NS update typeincluded in the second request is modifying a SAP instance, and SapInfoincluded in the second request is updated information about the SAP#2.2, where the first information is updated and includes: an identifierof a VL #11, an identifier of a port through which the SAP #2.2 isexternally connected to an external peer connection point through the VL#11, and an identifier of a peer connection point (to be specific, aservice access point ExtVnfCP #3.1 of a VNF #3 (not shown)) connected tothe SAP #2.2 through the VL #11. In this case, the second NFVO mayupdate, based on the updated information about the SAP #2.2, an externalconnection that is of the nested NS #2 and that is based on the SAP#2.2, in other words, update a network connection associated with thenested NS instance.

For still another example, in the examples in FIG. 13, for the secondNFVO that manages the nested NS #2, it is assumed that the NS updatetype included in the second request is removing a SAP instance, andSapInfo included in the second request is information about ato-be-removed SAP #2.3. In this case, the second NFVO may remove anexternal connection that is of the nested NS #2 and that is based on theSAP #2.2, in other words, remove a network connection associated withthe nested NS instance.

The foregoing examples are merely used to explain this application, andshall not constitute a limitation.

It may be understood that, the SapInfo is carried in a request (namely,the second request) used to update the nested NS instance, and theprovider NFVO may be indicated to update external and internal networkconnections of the nested NS instance based on the SapInfo from theperspective of the nested NS instance. This can better meet arequirement for updating a network connection from the perspective of anested NS.

In addition, a SAPD is extended in this application, to define a virtuallink information model from the perspective of the nested NS. Contentincluded in an extended SAPD may be shown in Table 4.

TABLE 4 Attribute Qualifier Cardinality Content Description attributequalifier cardinality content description SAP Mandatory 1 Boolean TheSAP address address value allocation describes allocation whether amanagement and orchestration function is responsible for the SAP addressallocation. If the Boolean value is set to be true, the manage- ment andorchestration function allocates an address to a SAP instance that iscreated by using the SAPD. Virtual Mandatory 0 . . . 1 IdentifierIdentifier of a link ID descriptor of a virtual descriptor linkconnectedto the ID SAP instance that is created by using the SAPD ID of anMandatory 0 . . . 1 Identifier Identifier of a associated ID descriptorof an connection external connection point point of a VNF or descriptorPNF, and identifier of the SAPD ID of an Mandatory 0 . . . 1 IdentifierIdentifier of a SAPD associated ID that is managed by a SAPD SAPinstance connect- ed to the SAP instance that, is created by using theSAPD Inherited All attributes inherit- attribute ed from a connectionpoint

In the extended SAPD shown in Table 4, such a newly added field, namely,the “ID of an associated SAPD” (associatedSapdID), defines an identifierof a SAPD associated with another SAP instance that is connected to theSAP instance created by using the SAPD shown in Table 4 in a designtime. In this way, the second NFVO may establish a correspondingconnection between SAP instances based on an association relationshipbetween SAPDs.

The following describes, by using several embodiments, implementation ofthe network service management method provided in this application indifferent application scenarios. For ease of description, a first NFVOis briefly referred to as an NFVO-1, and a second NFVO is brieflyreferred to as an NFVO-2 in the following several embodiments.

Embodiment 1

FIG. 14 shows a process of instantiating a composite NS by using atop-down method. The NFVO-1 initiates instantiation for each nested NS.This process mainly focuses on interaction performed through a referencepoint Or-Or.

Assumptions in the embodiment in FIG. 14 are as follows:

a. A mapping relationship <NSD, NFVO-2> is available for the NFVO-1.

b. There is no existing nested network service instance that can bedirectly used by a composite network service for instantiation. In otherwords, all nested NSs in the composite NS need to be created.

c. No nested NS instance is shared by another composite network service.

A process shown in FIG. 14 may be detailed as follows:

1. A sender (for example, an OSS/BSS) sends, to the NFVO-1, a requestused to create a composite NS. For specific implementation of this step,refer to clause 7.3.2 in the ETSI GS NFV-IFA013 protocol. Details arenot described herein again.

2. The NFVO-1 returns an ID of a composite NS instance to the sender.For specific implementation of this step, refer to clause 7.3.2 in theETSI GS NFV-IFA013 protocol. Details are not described herein again.

3. The NFVO-1 sends a composite NS ID creation notification to thesender. For specific implementation of this step, refer to clause8.3.2.9 in the ETSI GS NFV-IFA013 protocol. Details are not describedherein again.

4. The sender sends a composite NS instantiation request to the NFVO-1,where the request carries a nested NS ID. For specific implementation ofthis step, refer to clause 7.3.3 in the ETSI GS NFV-IFA013 protocol.Details are not described herein again.

5. The NFVO-1 returns a composite NS instantiation response to thesender. For specific implementation of this step, refer to clause 7.3.3in the ETSI GS NFV-IFA013 protocol. Details are not described hereinagain.

6. The NFVO-1 obtains a composite NSD used for instantiating thecomposite NS, and sends, to the sender, a composite NS life cycle changenotification that indicates a “start of instantiation”. For specificimplementation of this step, refer to clause 8.3.2.2 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

7. The NFVO-1 obtains, from the mapping relationship <NSD, NFVO-2>, anNFVO-2 corresponding to each nested NSD forming the composite NSD. Foreach member nested NS, the NFVO-1 sends a nested NS creation request(which is used to request to create a nested NS instance) to an NFVO-2that manages the nested NS, where the request may carry SapInfo. TheSapInfo may be used by the NFVO-2 to establish internal and externalnetwork connections that are based on a SAP instance of the nested NSinstance. For specific implementation of the SapInfo, refer to relatedforegoing descriptions. Details are not described herein again.

8. The NFVO-2 returns an ID of the nested NS instance to the NFVO-1.

9. The NFVO-2 sends a nested NS instance ID creation notification to theNFVO-1.

10. The NFVO-1 sends a nested NS instantiation request to the NFVO-2,where the request carries the ID of the nested NS instance and is usedto request to instantiate the nested NS.

11. The NFVO-2 returns a nested NS instantiation response to the NFVO-1.

12. The NFVO-2 sends, to the NFVO-1, a nested NS life cycle changenotification that indicates a “start of instantiation”.

13. The NFVO-2 performs a process of instantiating the nested NS.

14. As soon as the nest NS is successfully instantiated, the NFVO-2sends, to the NFVO-1, a life cycle change notification that indicates a“result”. For specific implementation of this step, refer to clause8.3.2.2 in the ETSI GS NFV-IFA013 protocol. Details are not describedherein again.

15. The NFVO-1 instantiates another member, such as a VNF or a PNF.

16. As soon as all members of the composite NS instance are successfullyinstantiated, the NFVO-1 sends a notification to the NFVO-2, to notifythe NFVO-2 that all member instances are successfully instantiated.

17. The NFVO-2 establishes, based on the SapInfo carried in the requestmessage, a connection between the nested NS instance and a memberinstance that is in the composite NS instance and that is (externally)connected to the nested instance through the SAP instance, and aconnection between the nested NS instance and a member instance that isin the nested NS instance and that is (internally) connected to thenested NS instance through the SAP instance.

18. As soon as all members in the composite NS instance are successfullyinstantiated, the NFVO-1 establishes a connection between other memberinstances (member instances other than the nested NS instance) and aconnection between each of the other member instances and the compositeNS instance.

19. The NFVO-2 returns a connection establishment success response tothe NFVO-1, to indicate that the internal and external networkconnections, formed through the SAP instance, of the nested NS instanceare successfully established.

20. The NFVO-1 sends, to the sender, a composite NS life cycle changenotification that indicates a “result”. For specific implementation ofthis step, refer to clause 8.3.2.2 in the ETSI GS NFV-IFA013 protocol.Details are not described herein again.

In this embodiment, the nested NS creation request in step 7 carries theSapInfo, and is equivalent to the first request mentioned in the methodprocedure in FIG. 12. The SapInfo may be used by the NFVO-2 to establishthe internal and external network connections that are based on the SAPinstance of the nested NS instance. Optionally, the SapInfo mayalternatively be carried in the nested NS instantiation request in step10. In this case, the nested NS instantiation request may be equivalentto the first request mentioned in the method procedure in FIG. 12.

In this embodiment, for step 17 for a specific implementation ofestablishing, by the second NFVO based on the SapInfo, connectionsindicated by a virtual link information model described by the SapInfo,refer to related content in the overall method procedure described inFIG. 12. Details are not described herein again.

In this embodiment, the connection between other member instances andthe connection between another member instance and the composite NSinstance that are mentioned in step 18 are network connections relatedto a non-nested NS instance. For example, in the examples in FIG. 13,the connection between other member instances includes a connectionbetween the VNF #2 and a SAP #5.2 that is of the composite NS instanceand that is connected to the VNF #2 at an external connection pointVnfExtCP #2.2 of the VNF #2 through a VL #9. The example is merely usedto explain this application, and shall not constitute a limitation.Optionally, the NFVO-1 may create a network connection between otherinstances by using a virtual link information model already defined inthe existing ETSI NFV standard. Details are not described herein again.

Embodiment 2

FIG. 15 provides a variant scenario of instantiating a composite NS. Inthis scenario, a nested NS instance in an instantiated composite NSinstance is an existing nested NS instance used by another composite NSinstance. Therefore, the nested NS instance is shared by a plurality ofcomposite NS instances, and the plurality of composite instances may beprovided in different administrative domains.

Assumptions in the embodiment in FIG. 15 are as follows:

a. A mapping relationship <nested NSD, NFVO-2> is available for theNFVO-1.

b. There is an existing nested NS instance that is managed by the NFVO-2and that can be directly used to instantiate a composite NS.

c. The NFVO-1 determines whether to use the existing nested NS instanceto constitute the composite NS.

With the assistance of the mapping relationship <nested NSD, NFVO-2>,the NFVO-1 may subscribe to a notification from the NFVO-2, where thenotification is used to capture, in an administrative domain in whichthe NFVO-2 is located, a status change of a nested NS instanceassociated with the nested NSD. A state of the nested NS instance mayinclude: being created but not instantiated, being instantiated but notshared, being instantiated and shared, or the like. The NFVO-1 mayfurther uses information about a state (for example, being instantiatedand shared) of the nested NS instance to instantiate the composite NS,for example, determine whether the nested NS instance may be used for anew composite NS.

A process shown in FIG. 15 may be detailed as follows:

1. The NFVO-2 subscribes to notifications that are of usage statuses ofNS instances and that are from all related NFVOs (including the NFVO-1).The related NFVO interacts with the NFVO-2 through an Or-Or referencepoint.

Herein, a manner in which an NFVO (for example, the NFVO-2 in thisembodiment) selects a group of NFVOs (the NFVO needs to subscribe tonotifications provided by the group of NFVOs) depends on a specificscenario. For example, in a proper manner, the NFVO may subscribe to anotification provided by each of other known NFVOs.

2. The NFVO-1 subscribes to a notification from the NFVO-2, to learn ofa status change of an NS instance (which is associated with an NSD or isdirectly indicated by the NFVO-1) in the administrative domain in whichthe NFVO-2 is located. A state of the NS instance may include: beingcreated but not instantiated, being instantiated but not shared, beinginstantiated and shared, or the like.

3. When a corresponding event occurs, the NFVO-2 sends an NS instancestatus change notification to the NFVO-1, where the notification maycarry an identifier of the NS instance and a new state of the NSinstance.

Steps 4 to 7 are the same as steps 1 to 4 in FIG. 14, and mainlydescribe a procedure in which a sender initiates a composite NSinstantiation request to the NFVO-1.

8. The NFVO-1 sends, to the NFVO-2, a notification of determining to usethe NS instance, to indicate that the NFVO-1 determines, based on astate (for example, being instantiated and shared) of the existing NSinstance and another limitation such as a capacity limitation of the NSinstance, to use the existing NS instance managed by the NFVO-2 toinstantiate the composite NS.

In response to the notification, the NFVO-2 may establish a userelationship between the existing NS instance and the NFVO-1.

It may be understood that when the NFVO-1 determines to use the existingNS instance managed by the NFVO-2 as a member NS instance, a SAPinstance for the existing NS instance needs to be newly added in acomposite NS managed by the NFVO-1. The newly added SAP instance may beused to establish a connection between the existing NS instance and amember instance in the composite NS managed by the NFVO-1, and thereforethe existing NS instance becomes a member instance in the composite NS.In this embodiment, the notification of determining to use the NSinstance may carry SapInfo associated with the newly added SAP instance,where the SapInfo is used by the NFVO-2 to establish a networkconnection that is based on the newly added SAP instance.

9. The NFVO-1 returns a composite NS instantiation response to thesender. For specific implementation of this step, refer to clause 7.3.3in the ETSI GS NFV-IFA013 protocol. Details are not described hereinagain.

10. The NFVO-1 obtains a composite NSD used for instantiating thecomposite NS, and sends, to the sender, a composite NS life cycle changenotification that indicates a “start of instantiation”. For specificimplementation of this step, refer to clause 8.3.2.2 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

11. The NFVO-1 instantiates another member, such as a VNF or a PNF.

12. As soon as all members of the composite NS instance are successfullyinstantiated, the NFVO-1 sends a notification to the NFVO-2, to notifythe NFVO-2 that all member instances are successfully instantiated.

13. The NFVO-2 may establish, by using the SapInfo, network connectionsthat are of the existing NS instance and that are based on the newlyadded SAP instance in the composite NS managed by the NFVO-1.Specifically, the NFVO-2 may establish a connection between the existingNS instance and a member instance that is in the composite NS instanceand that is (externally) connected to the existing NS instance throughthe newly added SAP instance, and a connection between the existing NSinstance and a member instance that is in the existing NS instance andthat is (internally) connected to the existing NS instance through thenewly added SAP instance.

14. The NFVO-2 returns a connection establishment success response tothe NFVO-1, to indicate that the network connections that are of theexisting NS instance and that are based on the newly added SAP instancein the composite NS managed by the NFVO-1 is successfully established.

15. The NFVO-1 uses the existing NS instance managed by the NFVO-2 toconstitute the composite NS instance.

16. The NFVO-1 sends, to the sender, a composite NS life cycle changenotification that indicates a “result”. For specific implementation ofthis step, refer to clause 8.3.2.2 in the ETSI GS NFV-IFA013 protocol.Details are not described herein again.

In this embodiment, the notification of determining to use the NSinstance in step 8 carries the SapInfo, where the SapInfo may be used bythe NFVO-2 to establish internal and external network connections thatare based on the newly added SAP instance of the existing NS instance.In this application, the notification of determining to use the NSinstance may be referred to as a third request.

In this embodiment, for step 13 for a specific implementation ofestablishing, by the second NFVO based on the SapInfo, connectionsindicated by a virtual link information model described by the SapInfo,refer to related content in the overall method procedure described inFIG. 12. Details are not described herein again.

Embodiment 3

FIG. 16 shows a process of instantiating a composite NS by using abottom-up method. A sender (an OSS/BSS) first initiates instantiationfor each nested NS before instantiation of the composite NS. Thisprocess mainly focuses on interaction performed through a referencepoint Or-Or.

Assumptions in the embodiment in FIG. 16 are as follows:

a. A mapping relationship <nested NSD, NFVO-2> is available for theNFVO-1.

b. No nested NS instance is shared by another composite NS.

A process shown in FIG. 16 may be detailed as follows:

1. The NFVO-1 subscribes to an NS life cycle change that is of a nestedNS and that is generated by the NFVO-2. For specific implementation ofthis step, refer to clause 7.4 in the ETSI GS NFV-IFA013 protocol.Details are not described herein again.

2. The sender (for example, the OSS/BSS) sends, to the NFVO-2, a requestused to create a nested NS ID. For specific implementation of this step,refer to clause 7.3.2 in the ETSI GS NFV-IFA013 protocol. Details arenot described herein again. Specifically, the request may carry SapInfo.The SapInfo may be used by the NFVO-2 to establish internal and externalnetwork connections that are based on a SAP instance of a nested NSinstance. For specific implementation of the SapInfo, refer to relatedforegoing descriptions. Details are not described herein again.

3. The NFVO-2 returns an ID of the nested NS instance to the sender. Forspecific implementation of this step, refer to clause 7.3.2 in the ETSIGS NFV-IFA013 protocol. Details are not described herein again.

4. The NFVO-2 sends a nested NS instance ID creation notification to thesender. For specific implementation of this step, refer to clause8.3.2.9 in the ETSI GS NFV-IFA013 protocol. Details are not describedherein again.

5. If the NFVO-1 already subscribes to the NS life cycle change(referring to step 1) that is of the nested NS and that is generated bythe NFVO-2, the NFVO-2 notifies the NFVO-1 of nested NS instance IDcreation.

6. The sender sends a nested NS instantiation request to the NFVO-2,where the request carries the ID of the nested NS instance. For specificimplementation of this step, refer to clause 7.3.3 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

7. The NFVO-2 returns a nested NS instantiation response to the sender.For specific implementation of this step, refer to clause 7.3.3 in theETSI GS NFV-IFA013 protocol. Details are not described herein again.

8. The NFVO-2 sends, to the sender, a nested NS life cycle changenotification that indicates a “start of instantiation”. For specificimplementation of this step, refer to clause 8.3.2.2 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

9. If the NFVO-1 already subscribes to the NS life cycle change(referring to step 1) that is of the nested NS and that is generated bythe NFVO-2, the NFVO-2 notifies the NFVO-1 of the nested NS life cyclechange notification that indicates a “start of instantiation”.

10. The NFVO-2 performs a process of instantiating the nested NS.

11. As soon as the nested NS instance is successfully instantiated, theNFVO-2 sends, to the sender, a nested NS life cycle change notificationthat indicates an “instantiation result”. For specific implementation ofthis step, refer to clause 8.3.2.2 in the ETSI GS NFV-IFA013 protocol.Details are not described herein again.

12. If the NFVO-1 already subscribes to the NS life cycle change(referring to step 1) that is of the nested NS and that is generated bythe NFVO-2, the NFVO-2 notifies the NFVO-1 of the nested NS instancelife cycle change notification that indicates an “instantiation result”.

13. As soon as all nested NS instances are successfully instantiated,the sender sends, to the NFVO-1, a request used to create a composite NSID. For specific implementation of this step, refer to clause 7.3.2 inthe ETSI GS NFV-IFA013 protocol. Details are not described herein again.

14. The NFVO-1 returns an ID of a composite NS instance to the sender.For specific implementation of this step, refer to clause 7.3.2 in theETSI GS NFV-IFA013 protocol. Details are not described herein again.

15. The NFVO-1 sends a composite NS ID creation notification to thesender. For specific implementation of this step, refer to clause8.3.2.9 in the ETSI GS NFV-IFA013 protocol. Details are not describedherein again.

16. The sender sends a composite NS instantiation request to the NFVO-1,where the request carries the ID of the nested NS instance. For specificimplementation of this step, refer to clause 7.3.3 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

17. The NFVO-1 returns a composite NS instantiation response to thesender. For specific implementation of this step, refer to clause 7.3.3in the ETSI GS NFV-IFA013 protocol. Details are not described hereinagain.

18. The NFVO-1 sends, to the sender, a composite NS life cycle changenotification that indicates a “start of instantiation”. For specificimplementation of this step, refer to clause 8.3.2.2 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

19. The NFVO-1 checks availability of a required nested NS instancebased on the notification in step 11.

20. If the composite NS includes a VNF and/or a PNF, the NFVO-1instantiates the VNF and/or the PNF.

21. As soon as all members of the composite NS instance are successfullyinstantiated, the NFVO-1 sends a notification to the NFVO-2, to notifythe NFVO-2 that all member instances are successfully instantiated.

22. The NFVO-2 establishes, based on the SapInfo, a connection betweenthe nested NS instance and a member instance that is in the composite NSinstance and that is (externally) connected to the nested instancethrough the SAP instance, and a connection between the nested NSinstance and a member instance that is in the nested NS instance andthat is (internally) connected to the nested NS instance through the SAPinstance.

23. The NFVO-2 returns a connection establishment success response tothe NFVO-1, to indicate that the internal and external networkconnections, formed through the SAP instance, of the nested NS instanceare successfully established.

24. As soon as all members in the composite NS instance are successfullyinstantiated, the NFVO-1 establishes a connection between other memberinstances (member instances other than the nested NS instance) and aconnection between each of the other member instances and the compositeNS instance.

25. The NFVO-1 sends, to the sender, a composite NS life cycle changenotification that indicates a “result”. For specific implementation ofthis step, refer to clause 8.3.2.2 in the ETSI GS NFV-IFA013 protocol.Details are not described herein again.

In this embodiment, the request used to create the nested NS ID in step2 carries the SapInfo, and is equivalent to the first request mentionedin the method procedure in FIG. 12. The SapInfo may be used by theNFVO-2 to establish the internal and external network connections thatare based on the SAP instance of the nested NS instance. Optionally, theSapInfo may alternatively be carried in the nested NS instantiationrequest in step 6. In this case, the nested NS instantiation request maybe equivalent to the first request mentioned in the method procedure inFIG. 12.

In this embodiment, for step 22 for a specific implementation ofestablishing, by the second NFVO based on the SapInfo, connectionsindicated by a virtual link information model described by the SapInfo,refer to related content in the overall method procedure described inFIG. 12. Details are not described herein again.

Embodiment 4

FIG. 17 shows a process of updating a composite NS. A composite NSmanaged by the NFVO-1 includes a nested NS managed by the NFVO-2. Thisprocess mainly focuses on interaction performed through a referencepoint Or-Or.

An NS update type associated with a nested NS instance may include butis not limited to: adding a SAP for the nested NS, modifying a SAP ofthe nested NS, removing a SAP of the nested NS, adding a nested NS, orremoving a nested NS. This embodiment mainly focuses on adding,modifying, or removing a SAP of the nested NS.

A process shown in FIG. 17 may be detailed as follows:

1. The NFVO-2 subscribes to notifications that are of usage statuses ofNS instances and that are from all related NFVOs (including the NFVO-1).The related NFVO interacts with the NFVO-2 through an Or-Or referencepoint.

Herein, a manner in which an NFVO (for example, the NFVO-2 in thisembodiment) selects a group of NFVOs (the NFVO needs to subscribe tonotifications provided by the group of NFVOs) depends on a specificscenario. For example, in a proper manner, the NFVO may subscribe to anotification provided by each of other known NFVOs.

2. A sender (for example, an OSS/BSS) sends, to the NFVO-1, a compositeNS update request used to perform an NS update operation. For specificimplementation of this step, refer to clause 7.3.5 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

3. The NFVO-1 returns an NS update response to the sender.

4. The NFVO-1 sends, to the sender, a composite NS life cycle changenotification that indicates a “start of an update”. For specificimplementation of this step, refer to clause 8.3.2.2 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

5. The NFVO-1 sends a nested NS instance update request to the NFVO-2,where the request carries SapInfo. The request may further include an NSupdate type, for example, adding a service access point or modifying aservice access point.

Specifically, the SapInfo may be information about all SAP instancesmanaged by the nested NS instance, or may be information about an addedSAP instance, information about a to-be-modified SAP instance, orinformation about a to-be-removed SAP instance. The SapInfo may be usedby the NFVO-2 to update a network connection associated with the nestedNS instance. For specific implementation of the SapInfo, refer torelated descriptions in the method procedure in FIG. 12. Details are notdescribed herein again.

6. The NFVO-2 updates the nested NS instance. Specifically, the NFVO-2may update the NS instance based on an NS update type, for example, addor modify a SAP instance.

7. The NFVO-2 returns a nested NS instance update success response tothe NFVO-1.

8. The NFVO-2 updates, based on the SapInfo, the network connectionassociated with the nested NS instance. Specifically, the updating anetwork connection associated with the nested NS instance may include atleast one of the following: establishing a new network connectionassociated with the nested NS instance, modifying an existing networkconnection associated with the nested NS instance, or removing anexisting network connection associated with the nested NS instance.

9. The NFVO-2 returns a connection update success response to theNFVO-1.

10. The NFVO-1 updates another member instance (a member instance, otherthan the nested NS instance, managed by the NFVO-2).

11. The NFVO-1 updates a network connection associated with the anothermember instance.

12. The NFVO-1 sends, to the sender, a composite NS life cycle changenotification that indicates an “update result”. For specificimplementation of this step, refer to clause 8.3.2.2 in the ETSI GSNFV-IFA013 protocol. Details are not described herein again.

In this embodiment, the nested NS instance update request in step 5carries the SapInfo, and is equivalent to the second request mentionedin the method procedure in FIG. 12.

In this embodiment, for step 8 for a specific implementation ofupdating, by the second NFVO based on the SapInfo, the networkconnection associated with the nested NS instance, refer to relatedcontent in the overall method procedure described in FIG. 12. Detailsare not described herein again.

FIG. 18 shows an apparatus 100 provided in this application. Theapparatus 100 may be applied in the NFV MANO system shown in FIG. 2. Theapparatus 100 may be mainly configured to implement a function of anNFVO. To be specific, the apparatus 100 mainly manages and processes anetwork service descriptor (NSD) and a virtualized network functionforwarding graph (VNFFG), and performs life cycle management for anetwork service. Optionally, the apparatus 100 may further integrate afunction of a VNFM, and may be further configured to perform life cyclemanagement for a VNF and implement a global view function forvirtualized resources. Optionally, the apparatus 100 may furtherintegrate a function of a VIM, and may be further configured to performresource allocation and/or reservation and exchange configuration andstatus information of a virtualized resource.

As shown in FIG. 18, the apparatus 100 may include a transceiver 103,one or more ports 107 coupled to the transceiver 103, a memory 105, anda processor 101 coupled to the memory 105.

The transceiver 103 may be a transmitter, a receiver, or a combinationthereof, and send or receive data through the port 107.

The memory 105 is coupled to the processor 101, and is configured tostore various software programs and/or a plurality of sets ofinstructions. Specifically, the memory 105 may be a high-speed randomaccess memory 105, and may further be a nonvolatile memory 105, forexample, one or more disk storage devices, a flash memory device, oranother nonvolatile solid-state storage device. The memory 105 may storean operating system (briefly referred to as a system below), forexample, an embedded operating system such as uCOS, VxWorks, or RTLinux.

In this application, the memory 105 may store an implementation program,namely, an NFVO module 1053, of the network service management methodprovided in one or more embodiments of this application. The NFVO module1053 may be executed on the processor 101. When the NFVO module 1053 isexecuted, the processor 101 may be configured to perform the networkservice management method provided in this application.

Optionally, the memory 105 may further store an NFV module 1051. The NFVmodule 1051 may be configured to host, store, and implement a networkfunction of one or more virtualized network devices.

The processor 101 may include one or more multi-core processors 101and/or the memory 105. The processor 101 may be a general purposeprocessor 101, an application-specific integrated circuit (ASIC), adigital signal processor 101 (DSP), or a system on chip (SoC). Theprocessor 101 is coupled to the transceiver 103, and may be configuredto process data received or sent by the transceiver 103. The processor101 may be configured to read and execute a computer-readableinstruction. Specifically, the processor 101 may be configured to:invoke a program stored in the memory 105, for example, animplementation program of the network service management method providedin one or more embodiments of this application, and execute aninstruction included in the program.

In this application, the apparatus 100 shown in FIG. 18 may beconfigured to run the consumer NFVO (that is, the first NFVO or theNFVO-1) mentioned in the foregoing method embodiments, or may beconfigured to run the provider NFVO (that is, the second NFVO or theNFVO-2) mentioned in the foregoing method embodiments.

Specifically, the apparatus 100 may be implemented as a computingapparatus such as a router, a server, or a switch.

It should be noted that the apparatus 100 shown in FIG. 18 is only animplementation of the embodiments of this application. In actualapplication, the apparatus 100 may further include more or fewercomponents, and this is not limited herein.

FIG. 19 shows an NFV MANO system and an apparatus provided in thisapplication. An NFV MANO system 10 may include a first apparatus 200 anda second apparatus 300. In this application, the first apparatus 200 maybe the consumer NFVO (that is, the first NFVO or the NFVO-1) mentionedin the foregoing method embodiments, and the second apparatus 300 may bethe provider NFVO (that is, the second NFVO or the NFVO-2) mentioned inthe foregoing method embodiments. The NFV MANO system 10 may be the NFVMANO system described in FIG. 2. Descriptions are separately providedbelow.

As shown in FIG. 19, the first apparatus 200 may include a processingunit 201 and a communications unit 203.

The communications unit 203 may be configured to receive a request thatis used to create a composite NS instance and that is sent by a sender(for example, an OSS/BSS).

The communications unit 203 may be configured to send a first request tothe second apparatus 300 (that is, the provider NFVO), where the firstrequest is used to request the second apparatus 300 to create a nestedNS instance in the composite NS instance.

The processing unit 201 may be configured to: create a member instance(that is, another member instance) other than the nested NS instance inthe composite NS instance, and establish a network connection betweenmember instances.

Specifically, the first request carries information about a SAP instanceassociated with the nested NS instance. The information about the SAPinstance may be used by the second apparatus 300 to establish, based onthe SAP instance, a connection between the nested NS instance and thecomposite NS instance and a connection between the nested NS instanceand the member instance in the composite NS instance, and is furtherused by the second apparatus 300 to establish, based on the SAPinstance, a connection relationship to a member instance in the nestedNS instance.

In this application, the member instance in the composite NS instancemay include at least one nested NS instance, and the member instance inthe nested NS instance may include at least one of the following: anested NS instance, a VNF instance, or a PNF instance.

In this application, the information about the SAP instance may includefirst information and second information. The first information may beused by the second apparatus 300 to establish, based on the SAPinstance, a connection relationship in which the nested NS instance isconnected to the member instance in the composite NS instance throughthe SAP instance. The second information may be used by the secondapparatus 300 to establish, based on the SAP instance, a connectionrelationship in which the nested NS instance is connected to the memberinstance in the nested NS instance through the SAP instance. Forspecific implementation of the SapInfo, refer to related descriptions inthe foregoing method embodiments. Details are not described hereinagain.

In some embodiments, the communications unit 203 may be furtherconfigured to receive a request that is used to update the composite NSinstance and that is sent by the sender (for example, the OSS/BSS). Thecommunications unit 203 may be further configured to send a secondrequest to the second apparatus 300, where the second request may beused to request to update the nested NS instance in the composite NSinstance. Specifically, the second request carries the information aboutthe SAP instance associated with the nested NS instance, and theinformation about the SAP instance may be used by the second apparatus300 to update, based on the SAP instance, a network connection that isassociated with the nested NS instance and that is in the composite NSinstance. Optionally, the processing unit 201 may be further configuredto: update the member instance (that is, the another member instance)other than the nested NS instance in the composite NS instance, andupdate the network connection between member instances.

In some embodiments, after receiving the request that is used to createthe composite NS instance and that is sent by the sender, thecommunications unit 203 may be further configured to send a thirdrequest to the second apparatus 300, where the third request may be usedto request to use an existing nested NS instance managed by the secondapparatus 300 to constitute a composite NS instance. Specifically, thethird request carries information about a SAP instance that is of theexisting nested NS instance and that is newly added in the composite NSinstance managed by the first apparatus 200. The information about thenewly added SAP instance may be used by the second apparatus 300 toestablish, based on the newly added SAP instance, a network connectionthat is of the existing nested NS instance and that is in the compositeNS instance.

It may be understood that for specific implementation of functionalunits included in the first apparatus 200, refer to the foregoing methodembodiments. Details are not described herein again.

As shown in FIG. 19, the second apparatus 300 may include a processingunit 301 and a receiving unit 303.

The receiving unit 303 may be configured to receive the first requestsent by the first apparatus 200 (that is, the consumer NFVO).Specifically, the first request carries the information about the SAPinstance associated with the nested NS instance, and is used to requestthe second apparatus 300 to establish the nested NS instance in thecomposite NS instance.

The processing unit 301 may be configured to establish, based on the SAPinstance and the information about the SAP instance, the connectionbetween the nested NS instance and the composite NS instance and theconnection between the nested NS instance and the member instance in thecomposite NS instance, and establish, based on the SAP instance and theinformation about the SAP instance, the connection relationship to themember instance in the nested NS instance.

In this application, the member instance in the composite NS instancemay include at least one nested NS instance, and the member instance inthe nested NS instance may include at least one of the following: anested NS instance, a VNF instance, or a PNF instance.

In this application, the information about the SAP instance may includethe first information and the second information. The first informationmay be used by the second apparatus 300 to establish, based on the SAPinstance, the connection relationship in which the nested NS instance isconnected to the member instance in the composite NS instance throughthe SAP instance. The second information may be used by the secondapparatus 300 to establish, based on the SAP instance, the connectionrelationship in which the nested NS instance is connected to the memberinstance in the nested NS instance through the SAP instance.Specifically, for specific implementation of the SapInfo, refer torelated descriptions in the foregoing method embodiments. Details arenot described herein again.

In some embodiments, the communications unit may be further configuredto receive the second request sent by the first apparatus 200, where thesecond request may be used to request to update the nested NS instancein the composite NS instance. Specifically, the second request carriesthe information about the SAP instance associated with the nested NSinstance, and the information about the SAP instance may be used by thesecond apparatus 300 to update, based on the SAP instance, the networkconnection that is associated with the nested NS instance and that is inthe composite NS instance. Correspondingly, the processing unit 301 maybe further configured to update, based on the SAP instance and theinformation about the SAP instance, the network connection that isassociated with the nested NS instance and that is in the composite NSinstance.

In some embodiments, the communications unit may be further configuredto receive the third request sent by the first apparatus 200, where thethird request may be used to request to use the existing nested NSinstance managed by the second apparatus 300. Specifically, the thirdrequest carries the information about the SAP instance that is of theexisting nested NS instance and that is newly added in the composite NSinstance managed by the first apparatus 200. The information about thenewly added SAP instance may be used by the second apparatus 300 toestablish, based on the newly added SAP instance, the network connectionthat is of the existing nested NS instance and that is in the compositeNS instance. Correspondingly, the processing unit 301 may be furtherconfigured to establish, based on the newly added SAP instance and theinformation about the newly added SAP instance, the network connectionthat is of the existing nested NS instance and that is in the compositeNS instance.

It may be understood that for specific implementation of functionalunits included in the second apparatus 300, refer to the foregoingmethod embodiments. Details are not described herein again.

In conclusion, by implementing of the technical solutions provided inthis application, the SapInfo is carried in a request (namely, the firstrequest) used to create the nested NS instance, and the provider NFVOmay be indicated to establish external and internal network connectionsof the nested NS instance based on the SapInfo from the perspective ofthe nested NS instance. This can meet a requirement for establishing anetwork connection from the perspective of a nested NS. In addition, theSapInfo is carried in a request (namely, the second request) used toupdate the nested NS instance, and the provider NFVO may be indicated toupdate external and internal network connections of the nested NSinstance based on the SapInfo from the perspective of the nested NSinstance. This can better meet a requirement for updating a networkconnection from the perspective of the nested NS.

A person of ordinary skill in the art may understand that all or some ofthe processes of the methods in the embodiments may be implemented by acomputer program instructing relevant hardware. The program may bestored in a computer-readable storage medium. When the program is run,the processes of the methods in the embodiments may be performed. Theforegoing storage medium includes any medium that can store programcode, such as a ROM, a random access memory RAM, a magnetic disk, or anoptical disc.

What is claimed is:
 1. A network service management method, comprising:receiving, by a second network functions virtualization orchestrator(NFVO), a first request sent by a first NFVO, wherein the first requestis used to request creating a nested network service instance in acomposite network service instance and carries information about aservice access point instance associated with the nested network serviceinstance; and establishing, by the second NFVO, a connection between thenested network service instance and the composite network serviceinstance and a connection between the nested network service instanceand a member instance in the composite network service instance based onthe service access point instance and the information about the serviceaccess point instance, and establishing a network connection between thenested network service instance and a member instance in the nestednetwork service instance based on the service access point instance andthe information about the service access point instance.
 2. The methodaccording to claim 1, wherein the information about the service accesspoint instance comprises first information and second information, thefirst information is used by the second NFVO to establish the connectionbetween the nested network service instance and the composite networkservice instance and the connection between the nested network serviceinstance and the member instance in the composite network serviceinstance based on the service access point instance, and the secondinformation is used by the second NFVO to establish the networkconnection to the member instance in the nested network service instancebased on the service access point instance.
 3. The method according toclaim 2, wherein the first information comprises an identifier of afirst virtual link instance, an identifier of a port through which theservice access point instance is connected to the first virtual linkinstance, and an identifier of a peer connection point connected to theservice access point instance through the first virtual link instance,wherein the first virtual link instance is used to externally connectthe nested network service instance to the member instance in thecomposite network service instance based on the service access pointinstance, and wherein the peer connection point connected to the serviceaccess point instance through the first virtual link instance is anexternal connection point that is of the member instance in thecomposite network service instance and that is connected to the serviceaccess point instance through the first virtual link instance.
 4. Themethod according to claim 3, wherein the member instance in thecomposite network service instance comprises at least one of anothernested network service instance, a virtualized network functioninstance, and a physical network function instance, and wherein theestablishing, by the second NFVO, of the connection between the nestednetwork service instance and the composite network service instance andof the connection between the nested network service instance and themember instance in the composite network service instance based on theservice access point instance and the information about the serviceaccess point instance comprises at least one of: establishing, by thesecond NFVO based on the service access point instance and the firstinformation, a connection between the service access point instance anda service access point instance that is of the composite network serviceinstance and that is externally connected to the service access pointinstance through the first virtual link instance; establishing, by thesecond NFVO based on the service access point instance and the firstinformation, a connection between the service access point instance anda service access point instance that is of the nested network serviceinstance in the composite network service instance and that isexternally connected to the service access point instance through thefirst virtual link instance; establishing, by the second NFVO based onthe service access point instance and the first information, aconnection between the service access point instance and an externalconnection point that is of the virtualized network function instance inthe composite network service instance and that is externally connectedto the service access point instance through the first virtual linkinstance; and establishing, by the second NFVO based on the serviceaccess point instance and the first information, a connection betweenthe service access point instance and an external connection point thatis of the physical network function instance in the composite networkservice instance and that is externally connected to the service accesspoint instance through the first virtual link instance.
 5. The methodaccording to claim 2, wherein the second information comprises at leastone of: an identifier of a second virtual link instance and a portthrough which the service access point instance is connected to thesecond virtual link instance; and an identifier of the second virtuallink instance, the port through which the service access point instanceis connected to the second virtual link instance, and an identifier of apeer connection point connected to the service access point instancethrough the second virtual link instance, wherein the peer connectionpoint connected to the service access point instance through the secondvirtual link instance is an external connection point that is of themember instance in the nested network service instance and that isconnected to the service access point instance through the secondvirtual link instance, and wherein the second virtual link instance isused to internally connect the nested network service instance to themember instance in the nested network service instance based on theservice access point instance.
 6. The method according to claim 5,wherein the member instance in the nested network service instancecomprises at least one of a sub-nested network service instance, avirtualized network function instance, and a physical network functioninstance, and wherein the establishing, by the second NFVO, of thenetwork connection between the nested network service instance and amember instance in the nested network service instance based on theservice access point instance and the information about the serviceaccess point instance comprises at least one of: establishing, by thesecond NFVO based on the service access point instance and the secondinformation, a connection between the service access point instance anda service access point instance that is of the sub-nested networkservice instance in the nested network service instance and that isinternally connected to the service access point instance through thesecond virtual link instance; establishing, by the second NFVO based onthe service access point instance and the second information, aconnection between the service access point instance and an externalconnection point that is of the virtualized network function instance inthe nested network service instance and that is internally connected tothe service access point instance through the second virtual linkinstance; and establishing, by the second NFVO based on the serviceaccess point instance and the second information, a connection betweenthe service access point instance and an external connection point thatis of the physical network function instance in the nested networkservice instance and that is internally connected to the service accesspoint instance through the second virtual link instance.
 7. The methodaccording to claim 1, further comprising: receiving, by the second NFVO,a second request sent by the first NFVO, wherein the second request isused to request updating of the nested network service instance in thecomposite network service instance and the second request carries theinformation about the service access point instance associated with thenested network service instance; and updating, by the second NFVO basedon the service access point instance and the information about theservice access point instance, a network connection that is associatedwith the nested network service instance and that is in the compositenetwork service instance.
 8. The method according to claim 1, furthercomprising: receiving, by the second NFVO, a third request sent by thefirst NFVO, wherein the third request is used to request using anexisting nested network service instance managed by the second NFVO andthe third request carries information about a service access pointinstance that is of the existing nested network service instance andthat is newly added in the composite network service instance managed bythe first NFVO; and establishing, by the second NFVO based on the newlyadded service access point instance and the information about the newlyadded service access point instance, a network connection that is of theexisting nested network service instance and that is in the compositenetwork service instance.
 9. A network service management method,comprising: sending, by a first network functions virtualizationorchestrator (NFVO), a first request to a second NFVO, wherein the firstrequest is used to request creating a nested network service instance ina composite network service instance and carries information about aservice access point instance associated with the nested network serviceinstance; receiving, by the second NFVO, the first request sent by thefirst NFVO; and establishing, by the second NFVO, a connection betweenthe nested network service instance and the composite network serviceinstance and a connection between the nested network service instanceand a member instance in the composite network service instance based onthe service access point instance and the information about the serviceaccess point instance, and establishing a network connection between thenested network service instance and a member instance in the nestednetwork service instance based on the service access point instance andthe information about the service access point instance.
 10. The methodaccording to claim 9, wherein the information about the service accesspoint instance comprises first information and second information, thefirst information is used by the second NFVO to establish the connectionbetween the nested network service instance and the composite networkservice instance and the connection between the nested network serviceinstance and the member instance in the composite network serviceinstance based on the service access point instance, and the secondinformation is used by the second NFVO to establish the networkconnection to the member instance in the nested network service instancebased on the service access point instance.
 11. The method according toclaim 10, wherein the first information comprises an identifier of afirst virtual link instance, an identifier of a port through which theservice access point instance is connected to the first virtual linkinstance, and an identifier of a peer connection point connected to theservice access point instance through the first virtual link instance,wherein the first virtual link instance is used to externally connectthe nested network service instance to the member instance in thecomposite network service instance based on the service access pointinstance, and wherein the peer connection point connected to the serviceaccess point instance through the first virtual link instance is anexternal connection point that is of the member instance in thecomposite network service instance and that is connected to the serviceaccess point instance through the first virtual link instance.
 12. Themethod according to claim 10, wherein the second information comprisesat least one of: an identifier of a second virtual link instance and aport through which the service access point instance is connected to thesecond virtual link instance; and an identifier of the second virtuallink instance, the port through which the service access point instanceis connected to the second virtual link instance, and an identifier of apeer connection point connected to the service access point instancethrough the second virtual link instance, wherein the peer connectionpoint connected to the service access point instance through the secondvirtual link instance is an external connection point that is of themember instance in the nested network service instance and that isconnected to the service access point instance through the secondvirtual link instance, and wherein the second virtual link instance isused to internally connect the nested network service instance to themember instance in the nested network service instance based on theservice access point instance.
 13. The method according to claim 9,further comprising: sending, by the first NFVO, a second request to thesecond NFVO, wherein the second request is used to request updating ofthe nested network service instance in the composite network serviceinstance and the second request carries the information about theservice access point instance associated with the nested network serviceinstance; receiving, by the second NFVO, the second request sent by thefirst NFVO; and establishing, by the second NFVO based on a newly addedservice access point instance and information about the newly addedservice access point instance, a network connection that is of anexisting nested network service instance and that is in the compositenetwork service instance.
 14. The method according to claim 9, furthercomprising: sending, by the first NFVO, a third request to the secondNFVO, wherein the third request is used to request using an existingnested network service instance managed by the second NFVO and the thirdrequest carries information about a service access point instance thatis of the existing nested network service instance and that is newlyadded in the composite network service instance managed by the firstNFVO; receiving, by the second NFVO, the third request sent by the firstNFVO; and establishing, by the second NFVO based on the newly addedservice access point instance and the information about the newly addedservice access point instance, a network connection that is of theexisting nested network service instance and that is in the compositenetwork service instance.
 15. An apparatus, comprising a receiving unitand a processing unit, wherein the receiving unit is configured toreceive a first request sent by a first network functions virtualizationorchestrator (NFVO), wherein the first request is used to requestcreating a nested network service instance in a composite networkservice instance and carries information about a service access pointinstance associated with the nested network service instance, andwherein the processing unit is configured to establish a connectionbetween the nested network service instance and the composite networkservice instance and a connection between the nested network serviceinstance and a member instance in the composite network service instancebased on the service access point instance and the information about theservice access point instance, and establish a network connectionbetween the nested network service instance and a member instance in thenested network service instance based on the service access pointinstance and the information about the service access point instance.16. The apparatus according to claim 15, wherein the information aboutthe service access point instance comprises first information and secondinformation, the first information is used by a second NFVO to establishthe connection between the nested network service instance and thecomposite network service instance and the connection between the nestednetwork service instance and the member instance in the compositenetwork service instance based on the service access point instance, andthe second information is used by the second NFVO to establish thenetwork connection to the member instance in the nested network serviceinstance based on the service access point instance.
 17. The apparatusaccording to claim 16, wherein the first information comprises anidentifier of a first virtual link instance, an identifier of a portthrough which the service access point instance is connected to thefirst virtual link instance, and an identifier of a peer connectionpoint connected to the service access point instance through the firstvirtual link instance, wherein the first virtual link instance is usedto externally connect the nested network service instance to the memberinstance in the composite network service instance based on the serviceaccess point instance, and wherein the peer connection point connectedto the service access point instance through the first virtual linkinstance is an external connection point that is of the member instancein the composite network service instance and that is connected to theservice access point instance through the first virtual link instance.18. The apparatus according to claim 17, wherein the member instance inthe composite network service instance comprises at least one of anothernested network service instance, a virtualized network functioninstance, and a physical network function instance, and wherein theprocessing unit is configured to establish the connecting between thenested network service instance and the composite network serviceinstance and the connection between the nested network service instanceand the member instance in the composite network service instance basedon the service access point instance and the information about theservice access point instance by at least one of: establishing, based onthe service access point instance and the first information, aconnection between the service access point instance and a serviceaccess point instance that is of the composite network service instanceand that is externally connected to the service access point instancethrough the first virtual link instance; establishing, based on theservice access point instance and the first information, a connectionbetween the service access point instance and a service access pointinstance that is of the nested network service instance in the compositenetwork service instance and that is externally connected to the serviceaccess point instance through the first virtual link instance;establishing, based on the service access point instance and the firstinformation, a connection between the service access point instance andan external connection point that is of the virtualized network functioninstance in the composite network service instance and that isexternally connected to the service access point instance through thefirst virtual link instance; and establishing, based on the serviceaccess point instance and the first information, a connection betweenthe service access point instance and an external connection point thatis of the physical network function instance in the composite networkservice instance and that is externally connected to the service accesspoint instance through the first virtual link instance.
 19. Theapparatus according to claim 16, wherein the second informationcomprises at least one of: an identifier of a second virtual linkinstance and a port through which the service access point instance isconnected to the second virtual link instance; and an identifier of thesecond virtual link instance, the port through which the service accesspoint instance is connected to the second virtual link instance, and anidentifier of a peer connection point connected to the service accesspoint instance through the second virtual link instance, wherein thepeer connection point connected to the service access point instancethrough the second virtual link instance is an external connection pointthat is of the member instance in the nested network service instanceand that is connected to the service access point instance through thesecond virtual link instance, and wherein the second virtual linkinstance is used to internally connect the nested network serviceinstance to the member instance in the nested network service instancebased on the service access point instance.
 20. The apparatus accordingto claim 19, wherein the member instance in the nested network serviceinstance comprises at least one of a sub-nested network serviceinstance, a virtualized network function instance, and a physicalnetwork function instance, and wherein the processing unit is configuredto establish the connection between the nested network service instanceand the composite network service instance and the connection betweenthe nested network service instance and the member instance in thecomposite network service instance based on the service access pointinstance and the information about the service access point instance byat least one of: establishing, based on the service access pointinstance and the second information, a connection between the serviceaccess point instance and a service access point instance that is of thesub-nested network service instance in the nested network serviceinstance and that is internally connected to the service access pointinstance through the second virtual link instance; establishing, basedon the service access point instance and the second information, aconnection between the service access point instance and an externalconnection point that is of the virtualized network function instance inthe nested network service instance and that is internally connected tothe service access point instance through the second virtual linkinstance; and establishing, based on the service access point instanceand the second information, a connection between the service accesspoint instance and an external connection point that is of the physicalnetwork function instance in the nested network service instance andthat is internally connected to the service access point instancethrough the second virtual link instance.